Wings not connecting
#Duplicate Port issue
native sinew
left smeltBOT
I have found the following for: https://ptero.co/oxiremofow
You already have an instance of Wings running through systemd service and are trying to start another duplicate instance, for example by using the commands wings and wings --debug, or another service is using the port.
Use ss -plnt | grep :8080 (or grep :8443 depending on the port) to find what process is currently running and stop it. You can type killall wings to shutdown any ghost Wings process.
native sinew
Access to XMLHttpRequest at 'https://node.legocraft.net:8080/api/system' from origin 'https://panel.legocraft.net' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header has a value 'https://panel.legocraft.net/' that is not equal to the supplied origin.
left smeltBOT
@native sinew Your Panel remote URL in the Wings config.yml does not match with the URL from which you're making the request. Make sure that they match for the connection to work.
If you know what you are doing and are intentionally trying to use a different origin, make sure to add it to your Wings config.yml allowed origins as shown in the example below. Use 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.
native sinew
nodes:1 Access to XMLHttpRequest at 'https://node.legocraft.net:8080/api/system' from origin 'https://panel.legocraft.net' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header has a value 'https://panel.legocraft.net/' that is not equal to the supplied origin.
jquery.min.js?t={cache-version}:4
GET https://node.legocraft.net:8080/api/system net::ERR_FAILED
@native sinew Your Panel remote URL in the Wings config.yml does not match with the URL from which you're making the request. Make sure that they match for the connection to work.
If you know what you are doing and are intentionally trying to use a different origin, make sure to add it to your Wings config.yml allowed origins as shown in the example below. Use 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.
native sinew
Access to XMLHttpRequest at 'https://node.legocraft.net:8080/api/system' from origin 'https://panel.legocraft.net' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header has a value 'https://panel.legocraft.net/' that is not equal to the supplied origin.Understand this error
jquery.min.js?t={cache-version}:4
GET https://node.legocraft.net:8080/api/system net::ERR_FAILED
@native sinew Your Panel remote URL in the Wings config.yml does not match with the URL from which you're making the request. Make sure that they match for the connection to work.
If you know what you are doing and are intentionally trying to use a different origin, make sure to add it to your Wings config.yml allowed origins as shown in the example below. Use 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.
left smeltBOT
You'll need to grab error logs for Wings and share the link with us. The following command will help you collect the required information for debugging: sudo wings diagnostics
native sinew
left smeltBOT
I have found the following for: https://ptero.co/ligukuwile
@native sinew; It looks like the Panel or Wings is responding too slowly, causing the request to timeout. Usually, this indicates some sort of a network issue.
Should the panel and wings be located on the same network, you might experience NAT reflection issues. In that case, type .nat for more information.
native sinew
left smeltBOT
I have found the following for: https://ptero.co/hekuyitebi
@native sinew 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.
native sinew
where is wings config file
fickle prairie
please provide the link given of running ls /var/log/pterodactyl* | nc pteropaste.com 99
native sinew
it is same remote url