eio | file blogging static auto-publishing platform | Incremental Backup library

I found out that that the port 0808 was being used by my servers router as a default gateway, so i changed the port and everything worked (:

It is because socket.example.com and app.example.com shares same domain and socket.example.com does not allow Cross origin request so throwing error when you are trying to connect from localhost. Try whitelisting localhost in socket.example.com's virtual host or try below solution.

Try this one.

In your virtual host file, change ServerName to test.example.com from localhost or create the virtualhost file like below if not present with name test.example.com.

I had the same issue. I solved it by downgrading socket.io to 2.2.0.

There appears to be some backward compatibility issues with SocketIO. You can uninstall python-engineio, python-socketio (and Flask-SocketIO just to be on the safe side) and reinstall lower versions.

The combination that worked for me was:

The Flask SocketIO documentation says this:

If an incoming HTTP or WebSocket request includes the Origin header, this header must match the scheme and host of the connection URL. In case of a mismatch, a 400 status code response is returned and the connection is rejected.

and this:

If necessary, the cors_allowed_origins option can be used to allow other origins. This argument can be set to a string to set a single allowed origin, or to a list to allow multiple origins. A special value of '*' can be used to instruct the server to allow all origins, but this should be done with care, as this could make the server vulnerable to Cross-Site Request Forgery (CSRF) attacks.

So instead of this:

I found the solution for my problem. Looks like you first need to access to the dynamic url serving your backend and click on "Continue". After doing that, CORS won't be a problem anymore.

This might be related to CORS problems. I had a similar issue where i had the socketio server running on port 5000, the angular app on 4200, which the CORS policy did not like at all. I solved this using a proxy configuration and starting the dev server with --proxy-config proxy.json.

proxy.json:

After following down the call stack I found this order (arrows represent calls, links are to the Linux source code).

v4l2_async_register_subdev -> v4l2_async_match_notify -> v4l2_device_register_subdev -> v4l2_ctrl_add_handler

The last function (v4l2_ctrl_add_handler) goes through and copies V4L2 controls from one handler to another.

Therefore, if the V4L2 control is not added before v4l2_async_register_subdev is called, then the control will not be copied to the different devices and will therefore not be a valid option available.

So in summation from what I found, no it is not possible to add V4L2 controls after the device has been registered.

Here's one way you could do something to try and communicate. If you host your own version of CORS Anywhere, you can communicate with http:// websites. I have a working link you can use, if you don't want to have to host one, but here the Github is. The way it works, is that you append the URL to the end of your URL for CORS Anywhere.

e.g https://cors.anywhere.com/google.com