search

zbx-sadman / unifi_proxy

Fast client-server version of UniFi Miner
45 stars 21 forks source link

Not working with Unifi 5.6.10 #11

Closed Haringstad closed 6 years ago

Haringstad commented 7 years ago

Great tool, stopped working with Unifi 5.6.10.......

Could you please look into that? Would be great if it starts working again!!!

Thank you for the superb work!

zbx-sadman commented 7 years ago

Hello

What kind of error you have?

Haringstad commented 7 years ago

I do not get an error, I do not get any values anymore.....

Just tell me what you would like me to do to provide you info....

Regards,

Jacco van Koll

On Wed, Jul 12, 2017 at 3:58 PM, Grigory Prigodin notifications@github.com wrote:

Hello

What kind of error you have?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zbx-sadman/unifi_proxy/issues/11#issuecomment-314777563, or mute the thread https://github.com/notifications/unsubscribe-auth/AHeCZiTPypzom11Kf3cPD2ezSzKjpNt_ks5sNND5gaJpZM4OVqeZ .

zbx-sadman commented 6 years ago

I have install fresh UniFi Controller v5.6.10 on the Windows, run UniFi Miner (CLI version of Proxy) in debug mode, and got communication error (HTTP status code 500).

Seems that UBNT use TLS 1.2 on default for this release.

I think that you can try one of this ways:

Send to me report, please.

Haringstad commented 6 years ago

After making changes:

zabbix_agentd -t "unifi.proxy[discovery,wlan]"; unifi.proxy[discovery,wlan] [s|{"data":[]}]

Still no salt ;-)

Running on Raspberry Pi, Raspbian Jessie

Regards,

Jacco van Koll

On Wed, Jul 12, 2017 at 8:50 PM, Grigory Prigodin notifications@github.com wrote:

I have install fresh UniFi Controller v5.6.10 on the Windows, run UniFi Miner (CLI version of Proxy) in debug mode, and got communication error (HTTP status code 500).

Seems that UBNT use TLS 1.2 on default for this release.

I think that you can try one of this ways:

  • Uncomment unifi.https.sslEnabledProtocols=TLSv1,SSLv2Hello string in the system.properties file, which placed into Controller's home dir ("C:\Users\Ubiquiti UniFi\data" on Windows) and restart the controller;
  • Change 'tlsv1' to 'TLSv12' string in the unifi_proxy.pl http://unifi_proxy.pl file (see for IO::Socket::SSL::set_default_context... line) and restart the Proxy;

Send to me report, please.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zbx-sadman/unifi_proxy/issues/11#issuecomment-314862394, or mute the thread https://github.com/notifications/unsubscribe-auth/AHeCZuDQkeLaWruPRN4bw2smEfb4N2Drks5sNRVkgaJpZM4OVqeZ .

zbx-sadman commented 6 years ago

Okay...

You need to get UniFi Miner and run it: _./unifiminer.pl -d 3 -c 0 > log.txt . Then you can see details of controller's HTTP respose in the log file and locate problem. And you can send the log file to me (email on my github main page).

Haringstad commented 6 years ago

That is working, and I do get data. I am now checking if this is caused by unifi.so (zabbix module), or by unifi_proxy.pl, by using the netcat option.

Regards,

Jacco van Koll

On Thu, Jul 13, 2017 at 9:55 AM, Grigory Prigodin notifications@github.com wrote:

Okay...

You need to get UniFi Miner https://github.com/zbx-sadman/unifi_miner and run it: ./unifi_miner.pl http://unifi_miner.pl -d 3 -c 0 > log.txt . Then you can see details of controller's HTTP respose in the log file and locate problem. And you can send the log file to me (email on my github main page).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zbx-sadman/unifi_proxy/issues/11#issuecomment-315001378, or mute the thread https://github.com/notifications/unsubscribe-auth/AHeCZrRIHOPyn3lIgqAyd0QUXeX60AUnks5sNc18gaJpZM4OVqeZ .

zbx-sadman commented 6 years ago

Note that you can enable debug output for Proxy too: unifi_proxy.conf -> DebugLevel=3. If you run it from command line without -D (daemonize) option - messages will be shown on console. One or two requests via netcat will allow to know what is wrong.

But do not forget about Cache TTL - Proxy can fetch data from local file and you can be confused.

Haringstad commented 6 years ago

It is weird, because, unifi_miner.pl DOES colllect proper data, but unifi_proxy.pl doesn't:

[22701] 2017-07-13 07:01:35 [+] handleConnection() started [22701] 2017-07-13 07:01:35 [.] Incoming line: 'discovery,uap' [22701] 2017-07-13 07:01:35 [+] fetchData() started [22701] 2017-07-13 07:01:35 [>] args: object type: 'site' [22701] 2017-07-13 07:01:35 [.] Object path: ' https://127.0.0.1:8443/api/self/sites' [22701] 2017-07-13 07:01:35 [.] Cache expire or not found. Renew... [22701] 2017-07-13 07:01:35 [.] Temporary cache file='/dev/shm/https___127_0_0_1_8443_api_self_sites.tmp' [22701] 2017-07-13 07:01:35 [+] fetchDataFromController() started [22701] 2017-07-13 07:01:35 [>] args: object path: ' https://127.0.0.1:8443/api/self/sites' [22701] 2017-07-13 07:01:36 [!] Comminication error: '500 Can't connect to 127.0.0.1:8443'

Regards,

Jacco van Koll

On Thu, Jul 13, 2017 at 12:13 PM, Grigory Prigodin <notifications@github.com

wrote:

Note that you can enable debug output for Proxy too: unifi_proxy.conf -> DebugLevel=3. If you run it from command line without -D (daemonize) option - messages will be shown on console. One or two requests via netcat will allow to know what is wrong.

But do not forget about Cache TTL - Proxy can fetch data from local file and you can be confused.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zbx-sadman/unifi_proxy/issues/11#issuecomment-315035902, or mute the thread https://github.com/notifications/unsubscribe-auth/AHeCZj4jhrerz_6CCEG1MdyaDhjWWsamks5sNe3OgaJpZM4OVqeZ .

Haringstad commented 6 years ago

Em, cannot find your e-mail address ??????

Regards,

Jacco van Koll

On Thu, Jul 13, 2017 at 1:03 PM, Jacco van Koll jacco.van.koll@gmail.com wrote:

It is weird, because, unifi_miner.pl DOES colllect proper data, but unifi_proxy.pl doesn't:

[22701] 2017-07-13 07:01:35 [+] handleConnection() started [22701] 2017-07-13 07:01:35 [.] Incoming line: 'discovery,uap' [22701] 2017-07-13 07:01:35 [+] fetchData() started [22701] 2017-07-13 07:01:35 [>] args: object type: 'site' [22701] 2017-07-13 07:01:35 [.] Object path: ' https://127.0.0.1:8443/api/self/sites' [22701] 2017-07-13 07:01:35 [.] Cache expire or not found. Renew... [22701] 2017-07-13 07:01:35 [.] Temporary cache file='/dev/shm/https___127_0_0_1_8443_api_self_sites.tmp' [22701] 2017-07-13 07:01:35 [+] fetchDataFromController() started [22701] 2017-07-13 07:01:35 [>] args: object path: ' https://127.0.0.1:8443/api/self/sites' [22701] 2017-07-13 07:01:36 [!] Comminication error: '500 Can't connect to 127.0.0.1:8443'

Regards,

Jacco van Koll

On Thu, Jul 13, 2017 at 12:13 PM, Grigory Prigodin < notifications@github.com> wrote:

Note that you can enable debug output for Proxy too: unifi_proxy.conf -> DebugLevel=3. If you run it from command line without -D (daemonize) option - messages will be shown on console. One or two requests via netcat will allow to know what is wrong.

But do not forget about Cache TTL - Proxy can fetch data from local file and you can be confused.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zbx-sadman/unifi_proxy/issues/11#issuecomment-315035902, or mute the thread https://github.com/notifications/unsubscribe-auth/AHeCZj4jhrerz_6CCEG1MdyaDhjWWsamks5sNe3OgaJpZM4OVqeZ .

zbx-sadman commented 6 years ago

Ough, really - no email on page now )) I'll fix it

zbx-sadman@gmail.com

Haringstad commented 6 years ago

Stuff is on it's way! Hey, we are all humans, and we all make mistakes! Most of the time I make them ;-)

Regards,

Jacco van Koll

On Thu, Jul 13, 2017 at 1:43 PM, Grigory Prigodin notifications@github.com wrote:

Ough, really - no email on page now )) I'll fix it

zbx-sadman@gmail.com

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zbx-sadman/unifi_proxy/issues/11#issuecomment-315053846, or mute the thread https://github.com/notifications/unsubscribe-auth/AHeCZvF5uTqpIAq-N7uqGxAykLCsr1qpks5sNgLIgaJpZM4OVqeZ .

davemuench commented 6 years ago

I ran into the same issue when upgrading my controller from 5.5.11 to 5.5.19, they must of made TLS 1.2 the default somewhere in there. Changing to "tlsv1_2" in unifi_proxy.pl fixed it for me.

Awesome Zabbix integration BTW - thank you!

zbx-sadman commented 6 years ago

TLS moved to 1.2 in v1.3.5 release