-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐞 [Bug]: Could get a free wireguard port on node 150 (devnet) #3508
Comments
Try using one relay in the stack and leave it one hour in case of cache and try again |
@khaledyoussef24 I appreciate that you include the problem in the title, because "can't deploy a VM" sounds like the whole grid is broken. |
it seemed broken to me because i could not deploy any vm on any node ,the issues is reproducible on my twin with all nodes. the issue after inspections was related to a few twins; one is mine. even when wireguard it turned off. @xmonader what do you recommend. |
related to threefoldtech/rmb-rs#200 (comment) should be working fine after the restart |
verified now i could use the old twin again and deployed a vm using it successfully |
Is there an existing issue for this?
which package/s did you face the problem with?
Dashboard
What happened?
was trying to create a machine without wireguard and disabled the option still getting an error that i can not create on the node because no wireguard port is empty
Steps To Reproduce
No response
which network/s did you face the problem on?
Dev
version
205fd89
Twin ID/s
No response
Node ID/s
129 156 160 165
Farm ID/s
No response
Contract ID/s
No response
Relevant screenshots/screen records
Relevant log output
na
The text was updated successfully, but these errors were encountered: