You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is the config with host names changed and tokens removed. Note I also tried ssl True under proxmox config.
"netbox_proxbox": {
"proxmox": {proxmox.example.net", # May also be IP address
"http_port": 8006,
"user": "root@pam", # always required
"password": "Strong@P4ssword", # only required, if you don't want to use token based authentication
"token": {
"name": "netbox", # Only type the token name and not the 'user@pam:tokenID' format
"value": "removed",
},
"ssl": False,
},
# The following json is optional and applies only for multi-cluster use
# {
# 'domain': 'proxbox2.example.com', # May also be IP address
# 'http_port': 8006,
# 'user': 'root@pam', # always required
# 'password': 'Strong@P4ssword', # only required, if you don't want to use token based authentication
# 'token': {
# 'name': 'tokenID', # Only type the token name and not the 'user@pam:tokenID' format
# 'value': '039az154-23b2-4be0-8d20-b66abc8c4686'
# },
# 'ssl': False
# }
"netbox": {
"domain": "proxmox.example.net", # Ensure localhost is added to ALLOWED_HOSTS
"http_port": 8001, # Gunicorn port.
"token": "removed",
"ssl": False, # There is no support to SSL on Netbox yet, so let it always False.
"settings": {"virtualmachine_role_id": 0, "node_role_id": 0, "site_id": 0},
The text was updated successfully, but these errors were encountered:
emersonfelipesp
added
bug
Further discussion is needed to determine this issue's scope and/or implementation
duplicate
This issue or pull request already exists
labels
Oct 24, 2024
How are you supposed to use this without SSL? Because as far as I can tell that is what the error is.
I get the following when doing a full update for the first time.
Poxmox 8.1
Here is the config with host names changed and tokens removed. Note I also tried ssl True under proxmox config.
The text was updated successfully, but these errors were encountered: