Docker/AdventureLog
Docker/AdventureLog
1
0
Fork 0
mirror of https://github.com/seanmorley15/AdventureLog.git synced 2025-07-19 04:49:37 +02:00
Code Issues Releases Activity

Update documentation/docs/troubleshooting/login_unresponsive.md

Browse source 
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This commit is contained in:
Sean Morley 2025-04-07 19:14:55 -04:00 • committed by GitHub
parent d2933854ff
commit 3b5240dffe
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

3
documentation/docs/troubleshooting/login_unresponsive.md
View file

@ -4,8 +4,7 @@ When you encounter issues with the login and registration pages being unresponsi
1. Check to make sure the backend container is running and accessible. 1. Check to make sure the backend container is running and accessible.
- Check the backend container logs to see if there are any errors or issues blocking the contianer from running. - Check the backend container logs to see if there are any errors or issues blocking the container from running.
2. Check the connection between the frontend and backend containers. 2. Check the connection between the frontend and backend containers.
- Attempt login with the browser console network tab open to see if there are any errors or issues with the connection between the frontend and backend containers. If there is a connection issue, the code will show an error like `Failed to load resource: net::ERR_CONNECTION_REFUSED`. If this is the case, check the `PUBLIC_SERVER_URL` in the frontend container and refer to the installation docs to ensure the correct URL is set. - Attempt login with the browser console network tab open to see if there are any errors or issues with the connection between the frontend and backend containers. If there is a connection issue, the code will show an error like `Failed to load resource: net::ERR_CONNECTION_REFUSED`. If this is the case, check the `PUBLIC_SERVER_URL` in the frontend container and refer to the installation docs to ensure the correct URL is set.