| 7 Apr 2024 |
 AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Well, is there a solution for this problem? Sorry if I'm repeating things that were already discussed! | 12:36:44 |
 TheFrenchGhosty | Comments are broken + healthcheck use comments endpoint = healthcheck see it as unhealthy | 12:36:49 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | This shouldn't contribute to the problem I'm having with the instance timing out, right? When I visit the URL of the instance, my browser reports that the connection timed out. | 12:37:30 |
| TheFrenchGhosty | This isn't at all relate | 12:38:13 |
| TheFrenchGhosty | * This isn't at all related | 12:38:18 |
 Midou | In reply to @thefrenchghosty:pussthecat.org
This has been discussed like 10 times in the last week alone... solution would be to add a FAQ | 12:43:01 |
| Midou | for known issues | 12:43:07 |
| Midou | and direct there when It gets too frequent | 12:43:21 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Now that we got that out of the way, let's tackle my other issue: Whenever I visit my newly deployed Invidious instance, I get a 504 Gateway Time-out. Why is that? My Invidious logs don't even display anything about someone visiting the instance. | 13:12:36 |
| Midou | In reply to @alexpewmaster:nope.chat
Now that we got that out of the way, let's tackle my other issue: Whenever I visit my newly deployed Invidious instance, I get a 504 Gateway Time-out. Why is that? My Invidious logs don't even display anything about someone visiting the instance. wrongly pointed proxy? | 13:18:38 |
| Midou | if invidious can't see someone that joined the instance, then it could be that your "proxy_pass" is not pointing to the right port, the right IP or any other factor that interfere with your connection between invidious and the reverse_proxy | 13:19:36 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | My Invidious instance is on the same machine as my reverse proxy, so I would point my Invidious domain to 127.0.0.1 in my reverse proxy, right? | 13:22:38 |
| Midou | yeah | 13:23:56 |
| Midou | also | 13:23:58 |
| Midou | if you're using docker, make sure it's not -"127.0.0.1:destport:incomingport" | 13:24:29 |
| Midou | remove the 127.0.0.1 if it's there | 13:24:41 |
| Midou | this part | 13:25:05 |
| Midou | 
Download clipboard.png | 13:25:05 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | My Invidious docker compose file doesn't have 127.0.0.1 in the ports section. | 13:25:22 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Should I share my docker compose file? | 13:26:16 |
| 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 |
