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
{{ message }}
This repository was archived by the owner on Feb 7, 2024. It is now read-only.
The fix in #31, i.e. DNS resolver, doesn't solve the issue for me.
The problem is that action() is used in HttpStatisticsLogger to push the stats. This is an issue for me, because the URL for HTTP is different for internal services than external users. Since the websockets server is running in its own container, I need it to reach out directly to my webserver container for it to work.
In this case, I have a websockets container and a caddy container, so I need HttpStatisticsLogger to make requests to http://caddy or whatever that IP resolves to (using Docker's DNS resolver).
Should we add an config('url') override as a config option? I think that might be the simplest way to solve this. I don't think it's a correct assumption that APP_URL will always allow a backend service to connect to itself.
The text was updated successfully, but these errors were encountered:
See #115, I wrote a simple implementation. We're stuck waiting until the project maintainers take a look at the open PRs.
In the meantime, you could just make your own fork with those changes if you urgently need them (or directly edit the code in vendor/ but that's a very temporary solution)
The fix in #31, i.e. DNS resolver, doesn't solve the issue for me.
The problem is that
action()
is used inHttpStatisticsLogger
to push the stats. This is an issue for me, because the URL for HTTP is different for internal services than external users. Since the websockets server is running in its own container, I need it to reach out directly to my webserver container for it to work.In this case, I have a
websockets
container and acaddy
container, so I needHttpStatisticsLogger
to make requests tohttp://caddy
or whatever that IP resolves to (using Docker's DNS resolver).Should we add an
config('url')
override as a config option? I think that might be the simplest way to solve this. I don't think it's a correct assumption that APP_URL will always allow a backend service to connect to itself.The text was updated successfully, but these errors were encountered: