This might be fixed by setting trusted_proxies = [ hosts.malobeo.hosts.fanny.network.address ]; to [ "127.0.0.1" "::1" ] (according to this ticket).
For this to work we need to make sure nginx is also running within the VM i think.
This might be fixed by setting `trusted_proxies = [ hosts.malobeo.hosts.fanny.network.address ];` to `[ "127.0.0.1" "::1" ]` (according to this [ticket](https://git.dynamicdiscord.de/malobeo/infrastructure/issues/72#issuecomment-828)).
For this to work we need to make sure nginx is also running within the VM i think.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I would take care of mimetipes and maybe header warnings the coming days, but would not consider this a blocker anymore
Mmh is the HTTPS warning new?
HAProxy should fix this for sure.
This might be fixed by setting
trusted_proxies = [ hosts.malobeo.hosts.fanny.network.address ];to[ "127.0.0.1" "::1" ](according to this ticket).For this to work we need to make sure nginx is also running within the VM i think.