keldwud / jitsi-party

Partying in the time of corona
MIT License
0 stars 0 forks source link

500 error after deployment #4

Open keldwud opened 3 years ago

keldwud commented 3 years ago

Failed to load resource: the server responded with a status of 500 (Internal Server Error)

500 Internal Server Error openresty/1.19.3.1

keldwud commented 3 years ago

This could just be due to not having enabled a config and a theme

keldwud commented 3 years ago

issue persists after setting the config and the theme then running make webpack && make restart; sleep 15; make db

keldwud commented 3 years ago

proxy logs

curl -k https://3.238.194.155

2021/08/10 18:41:13 [error] 214#214: *18 [lua] openidc.lua:570: openidc_discover(): accessing discovery url () failed: bad uri: , client: 3.238.194.155, server: ~.*, request: "GET / HTTP/1.1", host: "3.238.194.155"
2021/08/10 18:41:13 [error] 214#214: *18 [lua] access_by_lua(nginx.conf:125):26: accessing discovery url () failed: bad uri: , client: 3.238.194.155, server: ~.*, request: "GET / HTTP/1.1", host: "3.238.194.155"

proxy container is the only container showing new logs when the request is made

rene-grigory commented 3 years ago

How interesting. I'm able to bring everything up locally (I do have a theme and config set). When I run: docker-compose logs I see logs for all of the containers. However, when I run: make clean-theme and make clean-config the app still comes up...just with the default Jitsi stuff.

rene-grigory commented 3 years ago

Just did a make clean and recreated my .env, theme, and config...now I'm getting a 500 error. I suspect it's tied to the .env, but I can't really see how. The .env looks right to me.

keldwud commented 3 years ago

commented out (lines 347-351

PROXY_AUTH_ENABLED=
PROXY_AUTH_DISCOVERY=
PROXY_AUTH_CLIENT_SECRET=
PROXY_AUTH_ALLOWED_GROUPS=
PROXY_AUTH_CLIENT_ID=

but still receiving the 500 error. wiping containers and images and trying again

keldwud commented 3 years ago

make .env comment out PROXYAUTH* variables in .env

This resolves the 500 error issue

keldwud commented 3 years ago

https://asciinema.org/connect/96b05097-407b-4f4d-94d7-e25e954e9be1