Getting a 404 error when logging into our website using MBP. We can using other machines on same network

Ensure that the necessary certificates for HTTPS connections are configured and operating.

Translate DNS and verify you’re getting the expected translation in the client.

On the off chance an old translation is cached, flush the local DNS cache on the client:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

traceroute from client to the webserver host, and make sure you’re getting where you expect.

Verify that the webserver also has the expected DNS translation(s), too.

For completeness and as it can sometimes be confusing: the target webserver virtual host is selected by the webclient, that name is passed over the HTTP or HTTPS link, and the selected hostname or host address must then match a configured vhost in the webserver. So the client and the server must both agree on the selected vhost

Check the webserver log too, and verify the incoming connection arrives at the expected virtual host. The HTTP 404 errors should be Really Obvious in the webserver logs, too.

Maybe set up a default virtual host, if one is not configured.

Review and verify all rewrite rules are as expected on the webserver, too.

If needed, increase the logging level on the webserver, and teat again.

With what’s been posted so far, I see no reason (yet?) to be running any webclient re-installs.

TL;DR: check the webserver log

Check the DNS server settings, including the hosts file, on that computer. Perhaps someone was using it for testing and has the old server hard-coded in the hosts file.

Hi there Daily_llama, 

We understand that you have an issue isolated to a specific Mac and are unable to load a webpage. 

Let’s test a couple more things. Can we boot to safe mode and test there? Then next, create a new admin user and test there as well. These steps are going rule out some settings and software for us. 

Start up your Mac in safe mode

Set up users, guests, and groups on Mac

Thank you.

etresoft wrote:

It is almost as if some file on that machine is redirecting your DNS requests. I wonder what that file could be.

I can think of hosts of possibilities…

Maybe a different network route being used and the DNS propagation for the non-working device-connected network has not completed. Maybe you need to clear your browser cache.

It is almost as if some file on that machine is redirecting your DNS requests. I wonder what that file could be.