URL with non-standard port

  • I am contemplating a WordPress installation on my own, home, server. My ISP blocks port 80. Therefore, I need to use a non-standard port for accessing my server.

    The first question is, “will WordPress allow me to specify a port in the URL configured for the site?”.

    Assuming that WordPress can support a non-standard port the question becomes, “can the sites URL be changed subsequent to the initial installation?”. I suppose I am concerned about the possibility that URLs are generated/created that would subsequently become invalid.

Viewing 4 replies - 1 through 4 (of 4 total)

  • Give installing with a port a try, and see if it works and let everyone know. And look at Changing your site URL.

    But what are you going to do about DNS? Unless you’re on static IP, you need to deal with dynamic DNS.

    Thread Starter aajax

    (@aajax)

    I just finished getting WordPress working on my server. It is pretty slick on my own network.

    With respect to DNS I bought another domain to use for my blog. Even though my ISP service is on a dynamic IP I’ve found that it doesn’t get changed very often. It has been pretty satisfactory to manually update it when it does change. I’ve had the service for about a year and a half and the only time the address was changed was when I turned off my gateway when I was traveling for a couple of weeks.

    My hope is that URL forwarding might work. This allows me to specify the port on the URL to which my domain is being forwarded. This is good in the sense that it allows Internet users to see my site as being on the standard port (80). However, I’m not sure that Apache will be able to recognize the proper virtual host. I’ll post the findings after I’m done experimenting.

    Interesting to see that work. And there’s a dynamic DNS service.

    Thread Starter aajax

    (@aajax)

    It seems that URL forwarding does not work. At least one problem is that the host name in the HTTP header ends up containing the identity of the host to which the URL is forwarded which of course is going to be different from the host specified in the URLs generated by WordPress or for that matter the one publicized for users.

    On the other hand WordPress seems to accept the non-standard port number (in my case 60) on the options used to specify the URLs for both WordPress and the Blog. I haven’t been able to test very thoroughly just yet but the results so far are promising. It also looks like WordPress works fine even when the web server is listening on the standard port (80) and you simply forward the connections received by your gateway/router on the non-standard port to this standard port. However, because WordPress is now generating URLs that use the non-standard port, to make it work on both your internal network as well as the Internet you need to have the web server listening on the non-standard port. The downside to this approach is that users have to know to specify the non-standard port number when they enter the URL.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘URL with non-standard port’ is closed to new replies.

Tags