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
I ran into a networking issue when deploying to Fly.io and it turns out the cause was the nginx instance serving Swagger-UI wasn't binding to all ipv6 interfaces, only ipv4.
In the light of #8447, I've issued #8449. The change that we've introduced in #8438 is backward incompatible.
The PR #8449 makes the change backward compatible by disabling listen directive for IPv6 by default and with possibility to turn it on with PORT_IPV6 env variable.
Enabling IPv6 address and port for IPv6 addresses
caused backward incompatible issues in the docker image.
If one wants to use it, it must be turned on explicitly
with PORT_IPV6 env variable.
Refs #8447
Refs #8437
swagger-ui/docker/nginx.conf
Line 32 in f606c77
I ran into a networking issue when deploying to Fly.io and it turns out the cause was the nginx instance serving Swagger-UI wasn't binding to all ipv6 interfaces, only ipv4.
https://community.fly.io/t/private-networking-internal-domain-not-working-for-one-service/11096/7
It seems the solution is to simply add another
listen
directive:I can open a PR for this if needed. I need to fork the repo anyway in order to get Swagger-UI working in our Fly.io internal VPN.
The text was updated successfully, but these errors were encountered: