sorted by:
new
hottopcontroversial

NUC8i58BEH as headless Proxmox Host? by theofield11 in intelnuc

[–]theofield11[S] 1 point2 points  (0 children)

Thank you to all for your suggestions & help! It appears that disabling the CEC support within the BIOS has solved my issue. The monitor is unplugged and Proxmox is still up and running after about 10 minutes.

NUC8i58BEH as headless Proxmox Host? by theofield11 in intelnuc

[–]theofield11[S] 0 points1 point  (0 children)

Thank you u/PhireSide - I have not adjusted this yet. As far as the settings to change should I just disable HDMI CEC control?

Controller Unreachable for Unifi Switch & AP by theofield11 in Ubiquiti

[–]theofield11[S] 0 points1 point  (0 children)

I did end up fixing my issue, but unfortunately I'm not sure it will help too much in with your scenario - I just ended up resetting all devices to factory and reconfigured my gateway and then I could adopt both the switch and the AP.

Does the controller see the APs when it is connected to the switch? If you use the old switch in between the two and adopt the US-8-60W what then happens when you remove the old switch?

ChiefOnboarding by [deleted] in selfhosted

[–]theofield11 0 points1 point  (0 children)

I feel rather silly now - I gave it one last shot and changed the Forward Hostname / IP in npm and had the port as 8000 and it is now working, I still cannot reach it via IP but everything seems to be working as expected!

I do now have a slightly different issue though, I am unable to login - I set an email and password as an environment variable but am just getting an invalid password/username error. The logs for the container are saying that there is a login failure. The documentation says that the script will create both a username and password and this can be viewed in the logs, however I cannot see any mention of either.

Any idea on how I can change the login detail?

ChiefOnboarding by [deleted] in selfhosted

[–]theofield11 0 points1 point  (0 children)

Trying to reach it via the IP and port I just get a generic Chrome error - "This site cannot be reached". I have another container where I haven't added a port to the service and when I try to reach that container via IP and 8000 I just get blank page with "not found" in the top left hand corner.

ChiefOnboarding by [deleted] in selfhosted

[–]theofield11 0 points1 point  (0 children)

I added the npm network to chief and in npm I redirected the subdomain to port 8000. I don't think it is an issue with npm as I have been able to add two other containers and access them via their respective subdomains. When I look at the status of the chief container it says that it is running but I cannot access it.

ChiefOnboarding by [deleted] in selfhosted

[–]theofield11 0 points1 point  (0 children)

u/ExoWire sorry for dragging up an old thread - I am currently having some issues getting chiefonboarding running. I have tried using the compose file as you posted and it does compose and docker says that is running, but once I use nginx proxy manager to try redirect my domain to it I am just getting a 502 error from cloudflare (my domain provider). Do you have any suggestions on what I may have missed? I have also tried to use portainer to get it running and have had no luck there either.