Answered Home link showing as https://serverIP or https://localhost

Is this happening on more than one computer and more than one browser?

Yes, it happens both on my machine running chrome on osx and the clients computers running IE, chrome and firefox on windows.

I've PM'd you the domain name, I hope thats ok.

Quote from: howvard at Dec 09, 2014, 02:34 PM

Yes, it happens both on my machine running chrome on osx and the clients computers running IE, chrome and firefox on windows.

I've PM'd you the domain name, I hope that's ok.

It's fine. I don't see the effect, but I believe you. You might try disabling any plugins, especially ones connected to front-end events like OnHandleRequest.

Quote from: matdave at Dec 09, 2014, 04:21 PM

I had this issue on another site (also on RackSpace), I ended up creating a context setting to manually assign site_url and base_url. I don't know what ended up actually fixing it, but after a ton of server configuration changes, new sites don't experience this.

Do you create context settings on all of your new sites?

Quote from: BobRay at Dec 09, 2014, 10:20 PM

Quote from: howvard at Dec 09, 2014, 02:34 PM

Yes, it happens both on my machine running chrome on osx and the clients computers running IE, chrome and firefox on windows.

I've PM'd you the domain name, I hope that's ok.

It's fine. I don't see the effect, but I believe you. You might try disabling any plugins, especially ones connected to front-end events like OnHandleRequest.

The only plugin that was running when we first launched the site was wayfinder, the other plugins which have been added recently are get resources for a couple of the new pages. This issue only happens on the live site not on either of the development servers (however neither of these are with rackspace).

It's a mystery. The fact that it only happens at Rackspace suggests that it's a server issue, but the fact that it goes away when you clear the cache suggests that it could be something in MODX. My money would still be on it being caused by Rackspace.

Grepping the core/cache directory for 'localhost' after the problem occurs might provide a clue.

You might also grep the entire site's files for 'localhost' if you know how, and see if anything turns up other than the line in config.inc.php.

Similarly, you can export the entire database to a .sql file with PhpMyAdmin and search the file for 'localhost'.

Quote from: BobRay at Dec 10, 2014, 11:07 AM

It's a mystery. The fact that it only happens at Rackspace suggests that it's a server issue, but the fact that it goes away when you clear the cache suggests that it could be something in MODX. My money would still be on it being caused by Rackspace.

Grepping the core/cache directory for 'localhost' after the problem occurs might provide a clue.

You might also grep the entire site's files for 'localhost' if you know how, and see if anything turns up other than the line in config.inc.php.

Similarly, you can export the entire database to a .sql file with PhpMyAdmin and search the file for 'localhost'.

Hi BobRay,

Sorry for the delay in response.

I did check the files on the server and the database, although i didn't think about Grepping the cache when the error had occurred.

I do appear to have resolved the issue though, as suggested my matdave I created the following settings and the error seems to have disappeared.

base_url: /
site_url: http://www.domain.co.uk/

I've no idea why I had to do this as I've never had this issue anywhere else, maybe as matdave had this issue too its a rackspace setup quirk.

Thanks for everyones help!
Charles