Loading Profile...
How do you run Fixx on a remote machine through a domain name?
I haven't managed to find any information in the Fixx support pages for setting up Fixx on a webserver and accessing it via a domain name. I can install Fixx locally and access it through localhost:9000 but I really need to install it on a remote development machine (Mac running MAMP) and access it through a url like 'issues.example.com'. Is there a document root to speak of that I can point a domain at? Has anyone used Fixx with Mamp and can reassure me that it's possible?
Regards,
Paul Gregory
Regards,
Paul Gregory
I’m a bit confused
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
Hi Paul,
Sorry about the confusion in this regards. fixx should have no problem running with MAMP as long as MAMP is not using port 9000. Obviously, I am presuming you want to use MAMP for the MySQL bit? fixx doesn't really need Apache to run as it runs it's own web server.
In terms of pointing a domain name at it, it is just a matter of changing your DNS to point to the IP address of the fixx machine. Take a hypothetical example below,
I install fixx on a web-enabled machine with a public IP 67.13.38.10 (made up). I can access fixx at http://67.13.38.10:9000 as long as the firewall allows it. The only thing left to do is add a DNS record for example.com (A record if you are going to use sub-domains) like follows,
issues -> 67.13.38.10
Then you can access fixx at http://issues.example.com:9000
In summary, you really need to have experience of managing DNS (and I don't want to presume) to get this working. This is not specific to fixx at all, and applies to all servers.
I know that most of our customers use fixx from a publically available machine using a domain name (like we do), so it is definitely possible.
I’m hoping my explanation wasn't too technical.
The company and 1 other person say
this answers the question
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Paul,
Sorry about the confusion in this regards. fixx should have no problem running with MAMP as long as MAMP is not using port 9000. Obviously, I am presuming you want to use MAMP for the MySQL bit? fixx doesn't really need Apache to run as it runs it's own web server.
In terms of pointing a domain name at it, it is just a matter of changing your DNS to point to the IP address of the fixx machine. Take a hypothetical example below,
I install fixx on a web-enabled machine with a public IP 67.13.38.10 (made up). I can access fixx at http://67.13.38.10:9000 as long as the firewall allows it. The only thing left to do is add a DNS record for example.com (A record if you are going to use sub-domains) like follows,
issues -> 67.13.38.10
Then you can access fixx at http://issues.example.com:9000
In summary, you really need to have experience of managing DNS (and I don't want to presume) to get this working. This is not specific to fixx at all, and applies to all servers.
I know that most of our customers use fixx from a publically available machine using a domain name (like we do), so it is definitely possible.
I’m hoping my explanation wasn't too technical.
The company and 1 other person say
this answers the question
-
Inappropriate?thank you Sarat for your reply. This draws attention to a glaring oversight on my part. I had done all of the above apart from opening up port 9000 on the firewall. I'll try it in the morning. Thanks again for your excellent reply!
Paul
I’m thankful
1 person says
this answers the question
3 Comments Add a comment
This answers the question
-
That was one that tripped me up quite a few times, so I know exactly how it feels :) Hopefully that resolves the issue. -
Sorted out the firewall and worked great. Cheers, Sarat
-
Great news Paul. Glad to be of help.
EMPLOYEE
