¶ Client Configuration
The client is used to do all local communication between the site and your system. This allows all urls, apikeys, etc to stay local and requires apikey validation between the site and the client before any actions can be taken.
Going forward, it will be assumed you have configured the client already and have the port forwarded or the reverse proxy setup properly so the site can communicate with the client.
At the top of the Integration Setup page you will find the button to modify the settings for all the clients you have setup
The dialog for client settings is temporary until a more UX friendly way to manage all these settings is decided.
- Client list: Each client you have configured will show up as a tab so its settings can be modified
- This section is information about the local client and its host environment
- This is the URL to the client so the site can communicate with it
- Required for many features. Client will fallback to settings sync on a polling basis
- This cannot be any of the following which are local network
http://192.168.*.*:5454http://10.1.*.*:5454
- This can be
http://<your-external-ip>:5454- You may use any of the following commands to locate your external ip
curl ifconfig.mecurl -4/-6 icanhazip.comcurl ipinfo.io/ipcurl api.ipify.orgcurl checkip.dyndns.orgdig +short myip.opendns.com @resolver1.opendns.comhost myip.opendns.com resolver1.opendns.comcurl ident.mecurl bot.whatismyipaddress.comcurl ipecho.net/plain
- Note that you will be required to port forward your router to the system the Notifiarr client is running on.
- ISPs that are CGATS likely will need to use a VPS outside of their ISP to place the client on tunneled to the user's systems
- You may use any of the following commands to locate your external ip
- This can be
https://notifiarr.domain.comorhttps://domain.com/notifiarrif you use a reverse proxy with a port forward to point that reverse proxy port (http is 80 / https 443) to the local machine IP
- This is the connection status, if it isn't green then the site can not reach the client. Change the URL accordingly and click the icon to re-test until it turns green
- Client triggers: If the URL is provided, you can trigger the client to run any of these actions by clicking the cloud icon
- Bot trigger: If the URL is provided, you can pick a keyword and channel for the bot to monitor and it will give you the option to trigger any of the actions from all available clients
- Settings: The client needs to know how to handle each integration. Expand each one and configure them accordingly. Make sure the actual integration is enabled as well
- Save button: Once done, click this and it will update all your settings. If a URL is provided it will trigger the client to fetch the new settings right then. If no URL is provided then you can restart the client manually to pull the changed settings or wait 5 minutes for the client poller to request any changed settings and update
- If you have a duplicate client showup (change the user, hostname changed, etc) you can merge the new client with the old one so all the settings copy over and the old one is removed
- If you no longer have the client installed on a specific hostname, you can remove it
¶ Errors
- If the icon does not turn green, you can see the error and details in the Console via the Browser's DevTools (F12 in most browsers)
¶ Duplicate Clients
- This typically occurs in Docker or *BSD when a hostname is not configured everytime the container is restarted.
- For other installations this would occur if the unique attributes of your host system and installation change.
¶ Resolving Duplicate Clients
- Configure/Set a hostname for the client if applicable or resolve the changing attributes
- Restart the client
- On the Website in Client Configuration, Delete all client entries between the first and last client
- On the Website in Client Configuration, Merge the remaining two client entries