#Error with pannel loading

10 messages · Page 1 of 1 (latest)

jovial belfry
#

When i try to load the pannel for a server, everything work fine. But i can't see what is in the consol, I can't see what resources the server is using ect ect. I can see and manage file.

worn groveBOT
#

There were too many logs to read @jovial belfry. Please post 5 or less. Alternatively, please share larger logs using paste sites, such as pteropaste or hastebin.

jovial belfry
#

Error in firefox (frenche):
La connexion avec ws://xx.xx.xx.xx:8080/api/servers/892c830a-46b4-46ab-9012-f6d55273e0d1/ws a été interrompue pendant le chargement de la page. and a bunche of thing like this. All my port are opened and i really can't find where the problem is.

winged tartan
#

websocket: request origin not allowed by Upgrader.CheckOrigin

worn groveBOT
#

@winged tartan Your Panel remote URL in the Wings config.yml does not match with the URL from which you're making the request. Ignore the error if this is not you doing it.

If you know what you are doing and are intentionally trying to use a different origin such as when using API for websocket connection, make sure to add it to your Wings config.yml allowed origins as shown in the example below. Ue correct HTTP or HTTPS scheme. Wildcard '*' can be used to allow all origins.

allowed_origins:
- https://test.source.com
- http://another.panel.com

Restart Wings systemctl restart wings to apply the change.

jovial belfry
#

I did and I restarted wings but it still doesn't work

worn groveBOT
#

Please explain the issue you're experiencing in as much detail as possible. Preferably with error messages in a text format or paste link to logs. Nobody can assist you without information that helps to understand the issue. Help us help you. Messages such as "doesn't work" or "i need help" will most likely be ignored.

jovial belfry
worn groveBOT
#

I have found the following for: https://ptero.co/amexufolaq
@jovial belfry Your Panel remote URL in the Wings config.yml does not match with the URL from which you're making the request. Ignore the error if this is not you doing it.

If you know what you are doing and are intentionally trying to use a different origin such as when using API for websocket connection, make sure to add it to your Wings config.yml allowed origins as shown in the example below. Ue correct HTTP or HTTPS scheme. Wildcard '*' can be used to allow all origins.

allowed_origins:
- https://test.source.com
- http://another.panel.com

Restart Wings systemctl restart wings to apply the change.