Open julianfirminger-united opened 1 month ago
Hi @julianfirminger-united.
I had the same error. In my case, i changed the version of pynetbox, from 7.0.1 to 7.3.4 and it started to work, using this command inside my virtual-env:
pip install --force-reinstall -v "pynetbox==7.3.4"
The difference is located in: [7.0.1]pynetbox/core/query.py:184 vs [7.3.4]pynetbox/core/query.py:196
Hope it can help.
@ale456-1 turns out it needed more than that. the installer cant handle the new version number post v4 as it has 3 parts. 4.0.1 etc.
See thisfor the fix:
[((https://github.com/netbox-community/Device-Type-Library-Import/issues/142))]
@julianfirminger-united if you have valid ssl certs there's no issue, you can just run the install mentioned above. I highly recommend spending the 5 bucks a year to grab any old domain and taking the 10 minutes to generate a letsencrypt cert. My registrar has those off brand ones for $1 per year actually
Hi there, I can confirm workaround to reinstall pynetbox query per command
pip install --force-reinstall -v "pynetbox==7.3.4"
Quoting out the verification of Netbox version did not help me at this point. I switched backed and reinstalled pynetbox package so I am good to go right now.
regards Carsten
nb-dt-import.py fails with a 403. It seems to us it's ignoring the .env file?
I have a previous version running on rocky9.3 that works fine, we cant see a conf difference between them.
new nb4 on rokey9.4 does this:
Netbox runs fine, there is an api user with a token enabled. the .env file looks like: