I followed the guide to add Pocket-ID as a OIDC provider to my self hosted netbird instance on a vServer.
After setting up Pocket-ID localy on my TrueNAS, and filling out everything in NetBird to add Pocket-ID as a identity provider, I get the following error when hitting “Add Provider”
Pocked-ID is running on my TrueNAS with also the NeBird-App on it.
The truenas client ist visable and connected in the netbird dashboard,
but I can’t ping it for another client with netbird on it.
Even with the Default Policy All ↔ All.
Your explaination here is confusing me a little bit, most setups have netbird setup on an remote machine outside of the network. ALlowing Netbird and PocketID to communicate. In this case, Netbird cannot reach your Truenas/PocketID as it needs this for the openid-configfuration file
Sorry for the confusions, I have the NetBird self hosted on a external VPS with a puplic IP.
Here at home I have a NetBird-Client on my PC, my laptop and on my TrueNAS running.
So just going off-of assumptions here, if I had to guess. PocketID is behind your network, correct? Can Netbird connect from the external VPS to your home network TO the PocketID? Or are you trying to have PocketID authenticate internally through the netbird network itself?
Hi Xeravax,
thanks for the answers, I have PocketID running as a TrueNAS-app in a docker container, just like the NetBird-app. Do I need a NetBird client on the VPS to get PocketID as a OIDC in NetBird?
Should this be done with the Command-line installation:
curl -fsSL https://pkgs.netbird.io/install.sh | sh
Or should the
services:
netbird-client:
be added to the docker-compose.yaml from the netbird-server?
Or is it the better solution to install PocketID on the VPS via docker-compose? But properly I need the netbird peer on the netbird-server for the proxy-feature!?
Thanks for the help, I installed a NetBird-Client on my NetBird-VPS and added a policie to allow TCP port 80 and 443 to my TrueNAS with PockedID on it. Now it is working.