Non-standard ports

Support
1

For testing I often setup servers on a different port number. That way I don’t need to play with DNS and Host headers work.

I’m using a URL in the the standard form: http://host.domain.com:1234/uri
However, WebPageTest seems to break when testing against a non-standard port, reporting a ‘DNS lookup failed’.

Can this be fixed? It would make it easy to test and compare back-end server changes without affecting a live site.

2

Can you send me the domain (or even better, the full url) you are trying to test (pmeenan@webpagetest.org)? Non-standard ports work fine so I think there is a problem resolving the domain you are testing or something else going on.

Here is a test of the old pagetest hosting that was run on 8080: [url=http://www.webpagetest.org/result/090414_1CA5/]http://www.webpagetest.org/result/090414_1CA5/[/url]

Thanks,

-Pat

3

Man, I feel stupid.

Turns out this was a combination of BIND views, firewalls and load balancers conspiring against me.

Once I made the appropriate sacrifices to (of?) the network admins, it does seem to work.

Tks
:slight_smile:

4

Hello,

I am Starsrock.This is my first visit to site.I am new to this site,but I’ve enjoyed posting in your forums.Welcome to the forum.Some of you may have multiple virtual servers running on the same machine.Typically in such a setup each virtual server won’t have its own public IP Address,instead sharing the public IP of the host computer.This makes it a tad bit difficult to manage the virtual servers since using Remote Desktop to connect to the public IP will connect to the host computer and not the virtual machine.Thank you very much and Stay connected with me.