I signed up for the free account, and also tried the Pro account. In both instances I had the same issue. I'm running MAMP on a Mac. I setup a host domain at DynDNS. I can ping it, but if I enter it in a browser from within my network, I get a prompt for username and password from my router. I believe this is some kind of loop error. If I try to access the domain from outside my network, it either times out, OR I get the road runner search page.
I've tried port forwarding ports 80, 443, 8888, and it doesn't matter. I cannot reach my web server.
I've used the Mac updater and the one in my Linksys Router (separately), and I still get the same result. I cannot reach my server.
I've tested my ports via the suggested website and they're open. I cannot reach my server.
I've disabled my Firewall completely. I cannot reach my server.
I've followed at least 7 online tutorials exactly, and I get the same result. I cannot reach my server.
I've written to support. No response (I'm a paying customer).
I tried everything in the sticky and I still can't connect. I can only ping my hostname from my network. Going outside my network - all pings to my hostname time out. I'm too hesitant to give out my IP address so I hope this info helps. I have tried everything I know to try.
My DynDNS hostname: hapa.from-hi.com
All of a sudden it started working on an outside network even though I haven't changed any settings. It appends :8888 to the end of the URL though. How can I fix that?
UPDATE 3: ========= So do you mean that I should forward port 80 to 8888?
If I set Apache to listen on port 80 then forward port 80 it doesn't work. If I leave Apache on 8888 and forward 80 to 8888, it doesn't work. I can only get it to work if Apache is on port 8888, and I forward port 8888, but then when I enter the hostname it appends :8888 to the end of the url.
Moving the admin page to port 8080 doesn't work. I can no longer reach the server. I really wish there was an easy answer here.
UPDATE 5: ========= I did exactly that and just triple checked everything to make sure I did it right. No dice. Now I get a host not found error. I even tried it with an external webhop and a cname record and it doesn't work. Maybe I have a hardware problem, but I doubt it. The weird thing is that I can VPN right into my hostname after forwarding port 5900. That makes NO sense. I've tried so many ports and only port 8888 works, but appends :8888 to the end of the url.
UPDATE 6: ========= Here's what I have: Apache is on port 8888. I've forwarded port 80 to 8888, and port 8888 to 8888. I've moved the admin page to port 8080 (and I've also tried 442, and 443). It just times out. The webhop appears to be setup correctly.
From outside my network I type in oyer.from-hi.com, it turns to oyer.from-hi.com:8888 in the browser, but the status bar says "connecting to hapa.from-hi.com" but it never connects. It just times out. From inside my network I can only access it using 192.168.1.120:8888.
I'm really trying to dump the 8888. No matter what I do I can't get rid of that.
Okay, now I'm really confused. If you read the whole chain you'll see I was told to create the webhop and forward ports 80 and 8888 to 8888. How about this? What port should Apache be listening to? 80 or 8888? Or does it matter? All I need is one domain pointing to this server and for it to resolve without appending anything to the end of the URL. That's it.
What does this mean? " update your Apache configuration to support oyer.from-hi.com"
I understand it but it doesn't work. I put apache on port 80, open port 80 on my router, forward it, and it doesn't work. I've confirmed port 80 is open (no blocking) and yet it doesn't work. It's not meant to be.
I'm forwarding port 80 because that's the only way it works. I've reset Apache to be on port 80, I'm forwarding port 80 from my router. Please test it again and see what you get. It doesn't work for me unless I use port 8888 but I'm leaving it on 80 so someone can tell me what I'm doing wrong.
If your router supports port translation, then yes, this is indeed an option to try. But you said it doesn't work: "If I leave Apache on 8888 and forward 80 to 8888, it doesn't work."
Another option would be to use a webhop redirect.
For me it works now: http://hapa.from-hi.com/ redirects to http://oyer.from-hi.com:8888/, and your WordPress page appears, although some CSS still seems to be missing, but this is another topic. A hint though: add this trailing slash also to your webhop URL, this belongs to this URL and speeds up loading.
For me it still works, even better. The CSS problem is solved too, and everything comes up including formatting and pictures.
In case you don't want to see the port in the URL, it does matter. Only the standard port 80 is not to appear in the URL, any other (non-standard) port must appear or must be entered. From a technical side you can use any port as long as it works.
Then you must use port 80, if this works for you, and your ISP or your router don't prevent you from doing so. What's so difficult to understand here?
I find that your hostname
But for port 80 the Open Port Tool says:
Please work through this sticky and if you need further help edit your question to include all the information listed at the end of that guide.
The problem is that you've configured Apache to redirect traffic to port 8888 if it comes in on port 80 (or possibly just any other port).
That I see that redirect, on your IP and on port 80, says that the port is open and correctly forwarded to your Apache server.
If you're unsure about how to resolve that redirect then I'd suggest making use of the Apache support options.