When accessing the page she tries to load lasts about 10 seconds and reloads again and stays in that loop without stopping. When accessing the server I saw that at each attempt it shows this message in the log:
[error] Could not check origin for Phoenix.Socket transport.
Origin of the request: http://www.autoplacasma.com.br
This happens when you are attempting a socket connection to
a different host than the one configured in your config/
files. For example, in development the host is configured
to “localhost” but you may be trying to access it from
“127.0.0.1”. To fix this issue, you may either:
update [url: [host: …]] to your actual host in the
config file for your current environment (recommended)
pass the :check_origin option when configuring your
endpoint or when configuring the transport in your
UserSocket module, explicitly outlining which origins
are allowed:
check_origin: [“https://example.com”, “//another.com:888”, “//other.com”]
indicates the origin (scheme, hostname, and port) that **caused** the request
Caused… which is the website itself you connected to in the first place (ah-ah moment to me… this explains why I find domain names in the “check_origin”!)
What is the proper origin? You are conveniently told that by the console error (which I got with the default check_origin: true config):
[error] Could not check origin for Phoenix.Socket transport.
Origin of the request: https://mygoodservice.com:8443
I suspect that just letting the default value true is not actually defaulting to the origin you are prompted about in the console … (maybe it’s forgetting the port? or I’m doing bad somwhere else… dunno).
Anyway setting the whole exact string reported by the console solved for me!
Also: if you are troubleshooting start/stop/restarting your service, I’d close the tab and open a new one… for what is worth I’ve seen strange things happening on firefox (which might well be consequence of me doing this late night).
I’m late to the game, but using Phoenix v1.7.11 on Fly.io the following showed up in my logs:
This happens when you are attempting a socket connection to a different host than the one configured in your config/files. For example, in development the host is configured
to "localhost" but you may be trying to access it from "127.0.0.1". To fix this issue, you may either:
1. update [url: [host: ...]] to your actual host in the config file for your current environment (recommended)
2. pass the :check_origin option when configuring your endpoint or when configuring the transport in your UserSocket module, explicitly outlining which origins are allowed:
check_origin: ["https://example.com", "//another.com:888", "//other.com"]
I added check_origin: ["https://my_domain.com"] and it worked.