Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

custom-login-markup error #3687

Open
chrisekelley opened this issue Feb 20, 2024 · 3 comments
Open

custom-login-markup error #3687

chrisekelley opened this issue Feb 20, 2024 · 3 comments

Comments

@chrisekelley
Copy link
Member

chrisekelley commented Feb 20, 2024

Current version: 4.0.1 rc

Login screen will not render:

image

ERROR Error: Uncaught (in promise): HttpErrorResponse: {"headers":{"normalizedNames":{},"lazyUpdate":null},"status":502,"statusText":"OK","url":"https://acuity.tangerinecentral.org/custom-login-markup","ok":false,"name":"HttpErrorResponse","message":"Http failure response for https://acuity.tangerinecentral.org/custom-login-markup: 502 OK","error":"\n\n\n<title>Error</title>\n<style>\nhtml { color-scheme: light dark; }\nbody { width: 35em; margin: 0 auto;\nfont-family: Tahoma, Verdana, Arial, sans-serif; }\n</style>\n\n\n

An error occurred.

\n

Sorry, the page you are looking for is currently unavailable.
\nPlease try again later.

\n

If you are the system administrator of this resource then you should check\nthe error log for details.

\n

Faithfully yours, nginx.

\n\n\n"}
at resolvePromise (zone.js:1265:35)

@chrisekelley
Copy link
Member Author

chrisekelley commented Feb 20, 2024

Debugging the error logs from server:

2024-02-20T20:38:52.055Z INFO AppService.install (/tangerine/server/src/app.service.ts:82:9) Installing...
/tangerine/server/node_modules/axios/lib/core/AxiosError.js:89
AxiosError.call(axiosError, error.message, code, config, request, response);
^
AxiosError: getaddrinfo EAI_AGAIN couchdb

--- snip ---

[nodemon] app crashed - waiting for file changes before starting...

@chrisekelley
Copy link
Member Author

After doing a docker restart server, the page rendered fine.

So - if you get this error, check if there was a crash in the server log.

@esurface
Copy link
Contributor

@chrisekelley -- can we close this as resolved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants