You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the latest update to the script this error shows up:
last but not least, run /usr/local/bin/activate_masternodes_synx as root to activate your nodes.
root@SYNX:~/vps# /usr/local/bin/activate_masternodes_synx
Created symlink from /etc/systemd/system/multi-user.target.wants/synx_n1.service to /etc/systemd/system/synx_n1.service.
Job for synx_n1.service failed because the control process exited with error code. See "systemctl status synx_n1.service" and "journalctl -xe" for details.
The text was updated successfully, but these errors were encountered:
I believe this has something to do with the IPV6, SYNX doesn't need a different IP for each masternode and (from the client) I see only IPV4's and Onion ips.
After the latest update to the script this error shows up:
last but not least, run /usr/local/bin/activate_masternodes_synx as root to activate your nodes.
root@SYNX:~/vps# /usr/local/bin/activate_masternodes_synx
Created symlink from /etc/systemd/system/multi-user.target.wants/synx_n1.service to /etc/systemd/system/synx_n1.service.
Job for synx_n1.service failed because the control process exited with error code. See "systemctl status synx_n1.service" and "journalctl -xe" for details.
The text was updated successfully, but these errors were encountered: