Serveradress not saved in probe.conf, when not available at setup about pythonminiprobe

[tryallthethings]

Can confirm this issue. Saw it just now when I installed the miniprobe on 2 machines

Please provide the username the script should run under [root]:
Please provide the desired name of your Mini Probe [Python MiniProbe]:
Please provide the Probe GID [df1acfd7-46e7-4687-bade-50a962929bc6]:
Please provide the IP/DNS name of the PRTG Core Server []: 192.168.178.35
PRTG Server can not be reached. Please make sure the server is reachable.
Do you still want to continue using this server [y/N]: y
Please provide the port the PRTG web server is listening to (IMPORTANT: Only SSL is supported)[443]:
Please provide the base interval for your sensors [60]:
Please provide the Probe Access Key as defined on the PRTG Core []: xxx
Please provide the path where the probe files are located [/home/roots/downloads/PythonMiniProbe/miniprobe]:
Do you want the mini probe flushing buffered and cached memory [y/N]: y
Do you want to enable debug logging (can create massive logfiles!) [y/N]:
How much subprocesses should be spawned for scanning [10]:

./miniprobe/probe.conf
Config file successfully written!
Creating Logrotation Config
Setting up runlevel
Changing File Permissions
0
Starting Mini Probe
[ ok ] Starting prtgprobe (via systemctl): prtgprobe.service.
0
Done. You now can start/stop the Mini Probe using '/etc/init.d/prtgprobe start' or '/etc/init.d/prtgprobe stop'

###Mini Probe Config File
protocol:1
name:Python MiniProbe
cleanmem:True
server:None
gid:df1acfd7-46e7-4687-bade-50a962929bc6
baseinterval:60
subprocs:10
key:xxxx
debug:False
port:443
announced:0

[tabascoterrier]

I've created a pull request that should fix this if someone would be kind enough to merge it.