-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Can't install Technitium in advanced (to set static IP) #159
Comments
Strange... so the network connected and the container updated, but failed installing dependencies which is only curl and sudo. |
Would you try
enter your IP as |
Fixed, thanks for reporting! |
It still fails for me, in the same way. |
after setting the static IP and Gateway IP? |
Yes, and that was trying twice, once each with https://github.com/tteck/Proxmox/raw/v3/ct/technitiumdns-v3.sh and https://github.com/tteck/Proxmox/raw/main/ct/technitiumdns-v3.sh |
I'll give it a try again after dinner. Thank you for responding so quickly. I learned about your repo last night from Reddit, and was blown away. I greatly appreciate your work on this! |
Just tried again failed in the same place, after the "Installing Dependencies..." text. |
Are you setting the subnet mask? |
Yeah, I'm specifying ip/netmask - 192.168.99.2/24 for the IP, and the gateway as just the IP |
after it fails, click on the LXC and click network to see if the IP and gateway addresses are there |
is the IP you are trying to use available? |
Yes, it's a new vlan with only the gateway (at .1) so far. This will be the dhcp server for the vlan. |
The reason I'm using advanced, is that when I use the defaults and assign a static address / vlan - technitium complains that I'm using a dhcp address (which is true when I use the defaults, but not true when I reassign the host to a vlan, assign a static in pve, and reboot the container) |
IPV6 is your issue. Disable IPV6 if possible |
When attempting to use the v3 installer for technitium, I select "Advanced' then defaults for everything, except IP address and VLAN.
The install proceeds correctly, then the script bails out prior to completing. Cannot log into the container via pve -> container console, as defaults chose automatic and it requests a password.
` ✓ Started LXC Container
✓ Set up Container OS
✓ Network Connected: 192.168.99.2
✓ Updated Container OS
The text was updated successfully, but these errors were encountered: