Hi Paul,
That's an interesting one!
A
302 status is generally given as a response for a redirect attempt. This might suggest that there are issues with your DNS record?
Some other things to try, off the top of my head:
You could try restarting your webserver, and checking the webserver configuration against our
recommended documentation. You might also try placing the application in Debug mode to see if you can get a stack trace with more information. See:
Finally, I wonder if it could be a filesystem permissions issue? You can try resetting those by running the following from the root AtoM installation directory:
- sudo chown -R www-data:www-data /usr/share/nginx/atom
I would then suggest restarting PHP-FPM, memcached, and clearing the application cache. You'll find instructions on how to restart these services on this page (they'll work for 2.3 as well):
Regards,