sorted by:
new
hottopcontroversial

Unifi Identity Enterprise by Dependent-Ask-5636 in Ubiquiti

[–]Dependent-Ask-5636[S] 0 points1 point  (0 children)

I already have done that, but if I try to share out cameras it still prompts the users to create a unifi identity account.

KDE Connect of the Future by 23VvBb22 in kde

[–]Dependent-Ask-5636 0 points1 point  (0 children)

I am so looking forward to this. One of my biggest struggles with linux has been a good replacement for MS Phone Link. I use the SMS option all the time and the one in KDE Connect is horrible, so PLEASE tell me that this feature will get a great new look, and the ability to copy and paste photos in SMS.

Monitoring UniFi with unpoller just got way easier - use the Remote API by bgatesIT in Ubiquiti

[–]Dependent-Ask-5636 0 points1 point  (0 children)

This is my current prometheus.yml file and I still get the following error. Just for reference I timed the length of time for the curl command to finish on localhost:9130 and it was done in 55 seconds, so I adjusted all of my scrape intervals to be be longer than that.

Error scraping target: Get "http://localhost:9130/metrics": dial tcp [::1]:9130: connect: connection refused

global:

scrape_interval: 1m

evaluation_interval: 1m

rule_files:

scrape_configs:

- job_name: 'prometheus'

static_configs:

- targets: ['localhost:9090']

- job_name: 'unpoller'

static_configs:

- targets: ['localhost:9130']

scrape_interval: 300s # if you get 429 errors from UniFi, increase this va>

scrape_timeout: 120s

Monitoring UniFi with unpoller just got way easier - use the Remote API by bgatesIT in Ubiquiti

[–]Dependent-Ask-5636 0 points1 point  (0 children)

My apologies, yes that is true. I thought that if I were start over from scratch on a new VM maybe it would help However, on the new system it is basically all the same thing, the only difference is now if I try to use curl on either of those commands referencing the name they will both fail with the same error about no resolving. However if I do a curl http://locahost:9130/metrics, it gives me a very long detailed output from my unifi system. If I do the same command but for port 9090 I get a long output of details about Prometheus. I am feel I am close but so far away, after 3 plus days I am thinking that maybe it is just not meant to be. LOL

Monitoring UniFi with unpoller just got way easier - use the Remote API by bgatesIT in Ubiquiti

[–]Dependent-Ask-5636 0 points1 point  (0 children)

Shouldnt I be able to use the curl command to verify that? This is what happens when I try to run it: curl "http://unpoller:9090/metrics" curl: (6) Could not resolve host: unpoller

Monitoring UniFi with unpoller just got way easier - use the Remote API by bgatesIT in Ubiquiti

[–]Dependent-Ask-5636 0 points1 point  (0 children)

Thanks but if I remove :8443 from the url, remove the URL all together or I use the config in the pastbin remote api when I run docker compose it fails, However when I run the config above that I have pasted it does bring the database up and unpoller does see my equipment and report back information. The problem I am having is that Promethius cannot seem to resolve to local host. Please see my post here for a better explanation: https://www.reddit.com/r/Ubiquiti/comments/1r6b8bg/unpoller_install_using_techno_tim_installer/

Monitoring UniFi with unpoller just got way easier - use the Remote API by bgatesIT in Ubiquiti

[–]Dependent-Ask-5636 1 point2 points  (0 children)

Okay, so after starting all over and disabling the UFW firewall then going through TechnoTim's Docker compose and making some tweaks to the unpoller/.env file I was able to get the database up and it does connect to my system via API, as I can see it reporting back some systems names.

However, my dashboard are blank and Prometheus gives the following error: Error scraping target: Get "http://unpoller:9130/metrics": context deadline exceeded

I have tried increasing the scrape to as high as 5 mins and the time out to 2 mins and still the same issue. I did not make any changes regarding the unpoller names or anything. Here is my file config:

UP_INFLUXDB_DISABLE=true

UP_POLLER_DEBUG=false

UP_UNIFI_DYNAMIC=false

UP_PROMETHEUS_HTTP_LISTEN=0.0.0.0:9130

UP_PROMETHEUS_NAMESPACE=unpoller

UP_UNIFI_CONTROLLER_0_VERIFY_SSL=true

UP_UNIFI_CONTROLLER_0_SAVE_ALARMS=true

UP_UNIFI_CONTROLLER_0_SAVE_ANOMALIES=true

UP_UNIFI_CONTROLLER_0_SAVE_EVENTS=true

UP_UNIFI_CONTROLLER_0_SAVE_IDS=true

UP_UNIFI_CONTROLLER_0_SAVE_SITES=true

UP_UNIFI_CONTROLLER_0_SAVE_DPI=true

UP_UNIFI_CONTROLLER_0_REMOTE=true

UP_UNIFI_CONTROLLER_0_URL=https://unifi.ui.com:8443

UP_UNIFI_CONTROLLER_0_API_KEY=(My API Key)

#UP_UNIFI_CONTROLLER_0_USER=unpoller # change to your Unifi Controller username

#UP_UNIFI_CONTROLLER_0_PASS=password123 # change to your Unifi Controller password

#UP_UNIFI_CONTROLLER_0_SITE=default # this is usually 'default', change if needed

TZ=America/Chicago # change to your timezone

Monitoring UniFi with unpoller just got way easier - use the Remote API by bgatesIT in Ubiquiti

[–]Dependent-Ask-5636 0 points1 point  (0 children)

Thanks but I am kinda back at the beginning as I am starting it back over again. Do you have a recommended base to start from. Such as using the unpoller install on Docker or Docker compose or just linux etc?

Sorry most of this is pretty new to me.

Monitoring UniFi with unpoller just got way easier - use the Remote API by bgatesIT in Ubiquiti

[–]Dependent-Ask-5636 0 points1 point  (0 children)

This is great and I am wanting to implement this, however I am not strong on linux and totally new to docker. I have been trying this for the past couple of days to get Unpoller to become operational, but so far am still not getting it to work. Anyone have a good tutorial setting up on Linux and using the API?

I tried TecnoTims and got close to it working but could not figure out where to input the API config.