Il faudrait faire ce qu'il demander, donc un "journalctl -xe" sur le VPS pour voir pourquoi le service refuse de redémarrer.
et voilà :
-- Support:
https://www.debian.org/support--
-- A stop job for unit glorytun-udp@tun0.service has finished.
--
-- The job identifier is 1062 and the job result is done.
Jun 15 11:23:34 vps-30998b9f systemd[1]: Starting Glorytun UDP on tun0...
-- Subject: A start job for unit glorytun-udp@tun0.service has begun execution
-- Defined-By: systemd
-- Support:
https://www.debian.org/support--
-- A start job for unit glorytun-udp@tun0.service has begun execution.
--
-- The job identifier is 1062.
Jun 15 11:23:34 vps-30998b9f glorytun-udp-run[7432]: error: `to' is not a valid IPADDR for bind
Jun 15 11:23:34 vps-30998b9f systemd[1]: glorytun-udp@tun0.service: Main process exited, code=exite
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support:
https://www.debian.org/support--
-- An ExecStart= process belonging to unit glorytun-udp@tun0.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Jun 15 11:23:40 vps-30998b9f ss-server[597]: getpeername: Transport endpoint is not connected
lines 2701-2723/2723 (END)
-- Support:
https://www.debian.org/supportJun 15 11:22:43 vps-30998b9f ss-server[597]: getpeername: Transport endpoint is not connected
Jun 15 11:23:10 vps-30998b9f ss-server[597]: getpeername: Transport endpoint is not connected
Jun 15 11:23:28 vps-30998b9f ss-server[597]: getpeername: Transport endpoint is not connected
Jun 15 11:23:34 vps-30998b9f systemd[1]: glorytun-udp@tun0.service: Start-post operation timed out. Stopping.
Jun 15 11:23:34 vps-30998b9f systemd[1]: glorytun-udp@tun0.service: Control process exited, code=killed, status=15/TERM
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support:
https://www.debian.org/support--
-- An ExecStartPost= process belonging to unit glorytun-udp@tun0.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 15.
Jun 15 11:23:34 vps-30998b9f systemd[1]: glorytun-udp@tun0.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support:
https://www.debian.org/support--
-- The unit glorytun-udp@tun0.service has entered the 'failed' state with result 'exit-code'.
Jun 15 11:23:34 vps-30998b9f systemd[1]: Failed to start Glorytun UDP on tun0.
-- Subject: A start job for unit glorytun-udp@tun0.service has failed
-- Defined-By: systemd
-- Support:
https://www.debian.org/support--
-- A start job for unit glorytun-udp@tun0.service has finished with a failure.
--
-- The job identifier is 1015 and the job result is failed.
Jun 15 11:23:34 vps-30998b9f systemd[1]: glorytun-udp@tun0.service: Service RestartSec=100ms expired, scheduling restart.
Jun 15 11:23:34 vps-30998b9f systemd[1]: glorytun-udp@tun0.service: Scheduled restart job, restart counter is at 2.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support:
https://www.debian.org/support--
-- Automatic restarting of the unit glorytun-udp@tun0.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Jun 15 11:23:34 vps-30998b9f systemd[1]: Stopped Glorytun UDP on tun0.
-- Subject: A stop job for unit glorytun-udp@tun0.service has finished
-- Defined-By: systemd
-- Support:
https://www.debian.org/support--
-- A stop job for unit glorytun-udp@tun0.service has finished.
--
-- The job identifier is 1062 and the job result is done.
Jun 15 11:23:34 vps-30998b9f systemd[1]: Starting Glorytun UDP on tun0...
-- Subject: A start job for unit glorytun-udp@tun0.service has begun execution
-- Defined-By: systemd
-- Support:
https://www.debian.org/support--
-- A start job for unit glorytun-udp@tun0.service has begun execution.
--
-- The job identifier is 1062.
Jun 15 11:23:34 vps-30998b9f glorytun-udp-run[7432]: error: `to' is not a valid IPADDR for bind
Jun 15 11:23:34 vps-30998b9f systemd[1]: glorytun-udp@tun0.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support:
https://www.debian.org/support--
-- An ExecStart= process belonging to unit glorytun-udp@tun0.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Jun 15 11:23:40 vps-30998b9f ss-server[597]: getpeername: Transport endpoint is not connected