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
Technically not an issue with the project, though I discovered a bug related to bad DNS using this package. In my case I use(d) Verizon Fios DNS servers, which decides to send marketing domains for unresolved lookups sending me to unallocated.barefruit.co.uk for the wsgi container instead of via it's docker address. Switching to Open DNS fixed my problem. Not sure where it was trying to do a different resolver lookup - probably a docker hostname lockup issue. Will try and do some more research though if someone else gets the 504 issue from the client on the web socket connection, check your DNS settings
The text was updated successfully, but these errors were encountered:
Technically not an issue with the project, though I discovered a bug related to bad DNS using this package. In my case I use(d) Verizon Fios DNS servers, which decides to send marketing domains for unresolved lookups sending me to unallocated.barefruit.co.uk for the wsgi container instead of via it's docker address. Switching to Open DNS fixed my problem. Not sure where it was trying to do a different resolver lookup - probably a docker hostname lockup issue. Will try and do some more research though if someone else gets the 504 issue from the client on the web socket connection, check your DNS settings
The text was updated successfully, but these errors were encountered: