You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by mrehanabbasi May 14, 2024
I recently migrated from 4.6.5-beta (simple-login/app) to v4.43.0 (simple-login/app-ci). All the emails are redirecting properly but I cannot access the UI via the browser and get 504 bad gateway error. I can't access the UI via the mobile app as well.
Upon inspecting the logs of the sl-app container, I keep getting this:
>>> init logging <<<
>>> init logging <<<
2024-05-13 17:34:12,240 - SL - DEBUG - 15885 - "/code/app/utils.py:17" - <module>() - - load words file: /code/local_da
ta/words.txt
2024-05-13 17:34:12,283 - SL - DEBUG - 15886 - "/code/app/utils.py:17" - <module>() - - load words file: /code/local_da
ta/words.txt
[2024-05-13 17:34:16 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:15885)
[2024-05-13 17:34:16 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:15886)
[2024-05-13 17:34:16 +0000] [15886] [INFO] Worker exiting (pid: 15886)
[2024-05-13 17:34:16 +0000] [15885] [INFO] Worker exiting (pid: 15885)
[2024-05-13 17:34:17 +0000] [15889] [INFO] Booting worker with pid: 15889
[2024-05-13 17:34:17 +0000] [15890] [INFO] Booting worker with pid: 15890
>>> URL: https://app.mydomain.com
MAX_NB_EMAIL_FREE_PLAN is not set, use 5 as default value
Paddle param not set
Upload files to local dir
>>> URL: https://app.mydomain.com
MAX_NB_EMAIL_FREE_PLAN is not set, use 5 as default value
Paddle param not set
Upload files to local dir
What seems to be the issue?
The text was updated successfully, but these errors were encountered:
Discussed in #2107
Originally posted by mrehanabbasi May 14, 2024
I recently migrated from 4.6.5-beta (simple-login/app) to v4.43.0 (simple-login/app-ci). All the emails are redirecting properly but I cannot access the UI via the browser and get 504 bad gateway error. I can't access the UI via the mobile app as well.
Upon inspecting the logs of the
sl-app
container, I keep getting this:What seems to be the issue?
The text was updated successfully, but these errors were encountered: