| 7 Apr 2024 |
 AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | I think I might have modified some things | 13:26:31 |
 Samantaz Fox | if you share your compose, make sure to use a pastebin service and to remove the confidential data (like the hmac key) | 13:46:03 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Alright, here is my docker-compose.yml file: https://bin.reallyaweso.me/?945bfd9951a1a961#AKrjG6FMThNmeXW4PVTKmJqjBQVUpaqkpkZ8xcCvzw6t | 13:58:35 |
| Samantaz Fox | your compose file looks good | 14:04:23 |
| Samantaz Fox | nothing in docker logs? | 14:04:48 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Nope, absolutely nothing | 14:05:02 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Only 500 GET errors | 14:05:06 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | * Only 500 GET errors from comments | 14:05:19 |
| Samantaz Fox | 500 errors are caused by the comments not loading | 14:05:20 |
| Samantaz Fox | you can fix that by commenting out the healthcheck section | 14:05:36 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | My reverse proxy is pointing to 127.0.0.1:3003, I don't know what's wrong | 14:05:50 |
| Samantaz Fox | if you go to your_domain:3003 can you access invidious? | 14:06:35 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | 
Download image.png | 14:06:59 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Huh? | 14:07:00 |
| Samantaz Fox | that's normal, ignore the warning | 14:10:15 |
| Samantaz Fox | (you're accessing invidious directly, without the reverse proxy) | 14:10:29 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Problem is, I can't get past that error for some reason | 14:10:49 |
| Samantaz Fox | ah, try with http:// | 14:11:04 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Same issue | 14:11:08 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | But using the IP address works | 14:11:13 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Hmm, there seems to be something wrong in my reverse proxy then, right? | 14:11:36 |
| Samantaz Fox | yep | 14:11:51 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Ah yes, the reverse proxy not working is my favorite problem. My networking setup is so rough and weird | 14:12:39 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Alright, I'll take a look at it. Thanks for the help! | 14:12:50 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Oh wait, just visiting the instance URL now gives me a 502 Bad Gateway error | 14:13:26 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | ... which is still a reverse proxy issue (I think) | 14:13:40 |
| Samantaz Fox | try to restart the container with https_only: true and external_port: 443 commented out, and try to connect to http://yourdomain:3003 again | 14:16:10 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | In reply to @samantazfox:pussthecat.org
try to restart the container with https_only: true and external_port: 443 commented out, and try to connect to http://yourdomain:3003 again Tried it and still not working. It might be my browser though (LibreWolf). | 14:17:36 |
| Samantaz Fox | I can confirm it works from here | 14:18:56 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | What browser are you using? | 14:19:14 |
