Server 2012 Client Issue

  • igendreau

    (@igendreau)


    9 years ago

    So I have installed WordPress on my Server running Windows Server 2012 using Web Platform Installer. If I access my site from the browser on the server, it works great. Using https://localhost:1234/mySite, I get to the front end and https://localhost:1234/mySite/wp-admin gets me to the admin side no problem.

    When I try accessing that install from another computer on my network using: https://myServer:1234/mySite, the front end loads, but doesn’t render right. It looks like old school 1995 website fonts and layout, but the content is there. If I try to go to https://myServer:1234/mySite/wp-admin, I get a webpage not available error (ERR_CONNECTION_REFUSED). I’m guessing it’s a permissions thing but I’ve given Full Control to IIS_IUSRS. Can someone point me in the right direction?

Viewing 1 replies (of 1 total)
  • catacaustic

    (@catacaustic)

    That’s a very common issue.

    It happens because WordPres works on one full URL for everything, so everything refers back to the URL that it was installed under. In your case, every file reference (CSS, JavaScript, images, etc) points back to https://localhost and because you’re looking at it from a differnt PC, localhost for that PC is not the actual server location.

    The way to fix this is to set the URL’s to the public version, not the local version, and work off that on every machine. There’s several database search-and-replace plugins that can do that, or as an alternative I always use this script (The version 2 one as it’s a bit easier.

Viewing 1 replies (of 1 total)
  • The topic ‘Server 2012 Client Issue’ is closed to new replies.