|
Real simple. I've been able to use DynDNS to keep my ip updated. The problem relates to ports. I'm trying to have a shared hosting package access local data at my home. My ISP blocks http over port 80, but I can come in on higher port numbers (i.e. 3500). Meanwhile, my shared hosting via Godaddy blocks all outgoing http requests except those on port 80. The solutions so far? 1. Upgrade my home internet to business class - $60 per month extra. 2. Upgrade my hosting to a dedicated virtual server - $25 per month extra + if I can't admin it myself, $130 per month extra for server admin = $155 per month extra. These are both bad options way beyond my price range. Is there a way I can use a service from DynDNS to take a http request from my shared hosting server, via port 80, and send it along to my local data server via the dynamic ip address, over port 3500, and thus return the data back to the php script on my server? |
|
Sure, every web proxy is your friend! There are millions of them! But be aware of possible security risks, because these web proxy servers are always "men in the middle". Beside this, did you try with port 443? This is more rarely blocked than port 80, no matter if outbound or inbound. And why not run HTTP over HTTPS port 443? |
|
The only solution is the one RotBlitz provided in the first paragraph of his answer then - use a proxy service. Alternatively change web hosts. |
|
The problem is that my outgoing requests can ONLY go over port 80, no other port - that's a server/hosting restriction. Ideally, if DYNDNS could not only keep my IP current, but would append the port I want to use (i.e. 3500) I'd be good to go. But I don't think DynDNS can do that - others suggests a web hob. But then I don't get the dynamic DNS / IP resolution I need... |
|
I think I found out how I can do this, although it still doesn't fix the problem with my external web server connecting to my local at home data server. You deal with the dynamic DNS with a HOST setup, and then you use a Web Hop to the HOST to append the port you need to use. I.e. http://site.dyndns.com Host 11.111.11.1111 http://siteport.dyndns.com WebHop http://site.dyndns.com:3500 Thus, I can have my server request "siteport.dyndns.com" and ultimately, it has the request routed to 11.111.11.1111:3500, which in turn is handled by my router and finds the hardware I need to access. Works flawlessly in the browser, but still fails when I try to implement it via php. No matter, you still would need outbound port 3500 opened with a webhop. If it works, it is open, although you may think only port 80 is.
Jun 01 at 08:11 AM
RotBlitz ♦
|