Problem - Oracle VPS - PUBLIC_IP is not valid

[foosroos]

Terms

• This request is not a duplicate of an existing issue.
• I have provided as much information as I can to help resolve this issue.

Description

Background:
I had run the script once and after entering the public key from my local server, neither machine was able to complete the ping test (waited several minutes with no activity). I cancelled the scripts on both machines. When I restarted the script on the VPS, entering any option would exit the script with no error message. I then deleted the wg0.conf on the VPS and tried running the script again.

Additional Details:
The VPS and client were actively running Zerotier at the time of running the script. In retrospect now, I see that the zt IP address was a cause for a problem, at least on the VPS; see below the journalctl -xeu [email protected]. Unfortunately I jumped the gun and deleted the wg0.conf file and now cannot even rebuild it.

Mar 14 01:11:56 instance-20230131-1201 systemd[1]: Starting WireGuard via wg-quick(8) for wg0...
░░ Subject: A start job for unit [email protected] has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit [email protected] has begun execution.
░░
░░ The job identifier is 7142.
Mar 14 01:11:56 instance-20230131-1201 wg-quick[24368]: [#] ip link add wg0 type wireguard
Mar 14 01:11:56 instance-20230131-1201 wg-quick[24368]: [#] wg setconf wg0 /dev/fd/63
Mar 14 01:11:56 instance-20230131-1201 wg-quick[24387]: Line unrecognized: '172.26.24.184'
Mar 14 01:11:56 instance-20230131-1201 wg-quick[24387]: Configuration parsing error
Mar 14 01:11:56 instance-20230131-1201 wg-quick[24368]: [#] ip link delete dev wg0
Mar 14 01:11:56 instance-20230131-1201 systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit [email protected] has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Mar 14 01:11:56 instance-20230131-1201 systemd[1]: [email protected]: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit [email protected] has entered the 'failed' state with result 'exit-code'.
Mar 14 01:11:56 instance-20230131-1201 systemd[1]: Failed to start WireGuard via wg-quick(8) for wg0.
░░ Subject: A start job for unit [email protected] has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit [email protected] has finished with a failure.
░░
░░ The job identifier is 7142 and the job result is failed.

steps-to-reproduce

1. sudo rm /etc/wireguard/wg0.conf
2. Run the Oracle_installer.sh script
3. Enter VPS ip address
4. Leave WG server, Client, and Port blank

Actual Behavior

Script returns

VPS Public IP: 129.80.184.26

The following networks have been found on your system. Please use a different network for your Wireguard Server & Client{}
10.0.0.95/24 172.26.24.184/16 172.17.0.1/16

Wireguard Server IP [10.1.0.1]:
Wireguard Client IP [10.1.0.2]:
Wireguard Port [55108]:
PUBLIC_IP is not a valid IP, exiting...
root@instance-20230131-1201:~#

Script Version

Oracle

VPS wireguard config (/etc/wireguard/wg0.conf)

No response

Local Server wireguard config (/etc/wireguard/wg0.conf)

No response