Proxmox installation "Trying to detect country"

[_gabriel]

perhaps a "skip country auto détection" button that kill traceroute ?

 

[mdim]

Still happening on a fresh install on version 8.1. Got past it by going to a shell (Alt+F3 for me) then killing the traceroute process (kill -9 <pid>).

 

[Datadudedev]

First post N00b here

The installer aborted and dumped me to root shell. There was no traceroute running (checked px ax | grep [t]raceroute) returned nothing.

Weirdly, the first attempt to install went fine because despite not detecting a country because the installer failed and duped to the CLI installer which worked fine. This only happened once and able to reproduce it.

Was able to install via the CLI.

 

[+DS_DV+]

i have this error every few years.
today on a DL380p behind a AVM Fritzbox 7530 AX
all on latest firmware.
But the unplugged lan workaround works every time

 

[cheiss]

Hi,

just to give an update: I have just sent out a patch-series, which should fix this issue: https://lists.proxmox.com/pipermail/pve-devel/2024-February/061677.html

Unfortunately - as evidenced by this thread, it is a very peculiar issue and more or less pure luck to reproduce. But all in all, this at least fixes a very weird interaction, which seems to have been the cause of the issue.

 

[muekno]

I had the same problem in GUI mode, tried Debug mode GUI, evberything is asked, ran smooth

 

[TheDilettante]

Had the same issue - was stopping with "trying to detect country...". Disconnecting Ethernet helped.

 

[+DS_DV+]

the last week i installed a few new pves
and did not get the problem.
i noticed that i so far exclusively got them on big servers like Dell Power Edge R310 or HP Pro Liont DL380p

maybe it has sth to do with their special hardware?

 

[proxale]

the last week i installed a few new pves
and did not get the problem.
i noticed that i so far exclusively got them on big servers like Dell Power Edge R310 or HP Pro Liont DL380p

maybe it has sth to do with their special hardware?

I encountered this issue for the first time installing ProxMox on a laptop with DHCP IP. However, this is also the first time I am installing ProxMox on other than server grade hardware.

Didn't have this problem when the network cable was unplugged. The ethernet adapter is a very common Realtek 8111/8168/8411 type.

 

[proxale]

Still happening on a fresh install on version 8.1. Got past it by going to a shell (Alt+F3 for me) then killing the traceroute process (kill -9 <pid>).

Thanks for this, killing traceroute worked for me.
Strangely, the same traceroute command executed successfully when I switched to tty3 while the original was still stuck.

 

[dada051]

I had the same problem. Just deactivate ad blocking in pihole to get the country detection working.

 

[templar]

Just deactivate ad blocking in pihole to get the country detection working.

That worked, thanks!
I used old ISO, 8.1, so I didn't test patch from @cheiss

 

[lanpow]

I ran into this issue installing Proxmox VE 8.2 (c96ad84eacbbcef299ab8f407f9602f832abb5ceb08a9aa288c1e1164df2da97) on my Dell R710.

I'm not that versed in Linux but after reading all the comments I decided to pull the additional NIC out of Riser 1. Ran the Graphical installation again, it sat at at 3% for about 3 mins "creating LV's" and the rest of the installation completed in about another 3-5 or so mins.

Tried it twice to see if it was consistent. Hope this helps some one.