| 7 Apr 2024 |
 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 |
| Samantaz Fox | tor | 14:19:18 |
| Samantaz Fox | but in all cases, it means that invidious is running well (port 3003 bypasses your reverse proxy) | 14:19:56 |
| Samantaz Fox | so check your proxy config ^^ | 14:20:10 |
 Nihilist OLD ACCOUNT !!!! | In reply to @alexpewmaster:nope.chat
What browser are you using? u can check my configs for reference https://git.datura.network/nihilist/Datura-Network/src/branch/main/1-Privacy-Front-Ends/invidious | 14:20:19 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Uhh, does NGINX Proxy Manager work well with Invidious? | 14:22:40 |
| AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Because I'm using that as my reverse proxy | 14:22:49 |
| Samantaz Fox | idk, sorry | 14:23:44 |
| Samantaz Fox | nginx does, it's all I know | 14:23:58 |
| Samantaz Fox | AlexPewMaster btw, you might want to add 127.0.0.1: before the port mapping in your docker-compose file | 14:25:29 |
| Samantaz Fox | that'll bind the container port to the local interface, preventing direct access to invidious (like I did earlier) | 14:26:16 |
