alex
df8d1adf15
- Replace all AdventureLog references with Voyage across ~102 files (7 case variants: AdventureLog, adventurelog, Adventurelog, ADVENTURELOG, AdventUrelog, AdventureLOG, adventure-log, adventure_log) - Rename brand, static, and documentation assets to use voyage naming - Rename install_adventurelog.sh → install_voyage.sh - Update README.md and voyage_overview.md to credit AdventureLog as the upstream project and Sean Morley as its original creator
2.2 KiB
Troubleshooting: Starting nginx: nginx failed! in the Backend Container
::: tip As of 1-10-2024, this should be resolved in the latest version of Voyage. If you are still experiencing this issue, please reach out to the Voyage community on Discord or GitHub for further assistance. :::
The Voyage backend container uses a built-in Nginx container with a built-in nginx config that relies on the name server to be the service name of the backend container. If the Nginx service fails to start in the backend container, the whole backend service will keep restarting and fail to start.
The primary reason for this error is changing the backend service name server to something different
If you're experiencing issues with the Nginx service failing to start in the backend container, follow these troubleshooting steps to resolve the issue.
1. Check the server Service Name:
- Verify that the service name of the backend container is set to
serverin thedocker-compose.ymlfile. - The service name should be set to
serverin thedocker-compose.ymlfile. For example:server: image: ghcr.io/seanmorley15/voyage-backend:latest container_name: voyage-backend
2. To keep the backend service name different:
-
If you want to keep the backend service name different from
server, you can mount a custom Nginx configuration file to the backend container.- Get the default Nginx configuration file from the Voyage repository:
wget https://raw.githubusercontent.com/seanmorley15/Voyage/refs/heads/main/backend/nginx.conf- Update the
nginx.conffile to replace all occurrences ofserverwith your custom service name. - Mount the custom Nginx configuration file to the backend container in the
docker-compose.ymlfile. For example:server: image: ghcr.io/seanmorley15/voyage-backend:latest container_name: voyage-backend volumes: - ./nginx.conf:/etc/nginx/nginx.conf
3. Restart the Backend Container:
These steps should help you resolve the issue with the Nginx service failing to start in the backend container. If you continue to face issues, please reach out to the Voyage community on Discord or GitHub for further assistance.