You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Did you check to see if this issue already exists?
Is this only a feature request? Do not put multiple feature requests in one issue.
Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.
Is your proposal related to a problem?
Outbound HTTP requests backend makes would fail if Lemmy instance has no direct outbound internet connection.
Describe the solution you'd like.
Please consider adding HTTP(S) proxy support for outgoing requests, HTTP_PROXY environment variable is an industry standard, of sorts. Config option would also work, of course.
Thanks in advance.
Describe alternatives you've considered.
I've thought about things like routing Lemmy backend container traffic via wireguard client container but I'd rather not. :)
Additional context
No response
The text was updated successfully, but these errors were encountered:
I've tried setting HTTP_PROXY for the lemmy (backend) container and it broke the whole thing for me, i.e. white page with "Server error" and that's it.
Proxy logs show that inter-container traffic within lemmy compose setup also goes through the proxy, which obviously is not aware of http://pictrs/... and any other non-fqdn names which only resolve inside the container. So those need to be excluded somehow.
Requirements
Is your proposal related to a problem?
Outbound HTTP requests backend makes would fail if Lemmy instance has no direct outbound internet connection.
Describe the solution you'd like.
Please consider adding HTTP(S) proxy support for outgoing requests, HTTP_PROXY environment variable is an industry standard, of sorts. Config option would also work, of course.
Thanks in advance.
Describe alternatives you've considered.
I've thought about things like routing Lemmy backend container traffic via wireguard client container but I'd rather not. :)
Additional context
No response
The text was updated successfully, but these errors were encountered: