I've noticed an update is available in my Dash to update to v250 - Does anyone have the release notes?
Marcus, would I need to reload your visualisations ?
Thanks
Hello VK2HIM, you should upgrade to v250 as it brings much more stability (my FLM02 didn't have an issue for a very very long time now); yes, then you have to reload the visualizations. Please be aware that I synced on FLM03, so there is a special branch/release for the v2 FLM visualizations now --> https://github.com/gebhardm/flmlocal/releases
Release notes are here --> https://www.flukso.net/content/v250-changelog
Best regards, merry christmas and a happy new year...
Markus
vk2him |
Thank you for the information Markus - I'll update in the next day and reload the visualisations - Merry Christmas and Happy New Year to you too!
Hi Markus,
I upgraded to v250 and reloaded visualisations plus chart functionality is working great - thanks!
I found one issue when following your instructions - during the scp the flm runs out of space because when cloning "git clone http://github.com/gebhardm/flmlocal", the downloaded www directory also contains a directory called "flmlocal" - this shouldn't exist. When you scp the local www directory it runs out of space when it gets to www/flmlocal. To fix, I deleted the flm's /www/flmlocal/ to free the space (rm -r /www/flmlocal) and then scp again after deleting the /www/flmlocal directory on my local disk.
Thanks again!
vk2him |
P.S. - maybe the extra flmlocal directory in www was my mistake as I can see that there is no flmlocal directory when manually looking at https://github.com/gebhardm/flmlocal ... I'd say I accidentally copied it twice :( All good now though :)
gebhardm |
git is full of wonders :-) I guess you cloned a second time while already being in a locally cloned flmlocal/www directory. If so, a git pull would have brought the latest version; mind the different flavors/branches for flm02 and flm03...
rs |
Hi Markus,
This is really very good news, using Mosquitto to the FLM on a RPI was too complicated for me but your flmlocal implementation works wonderfull.
I have to study on the Graph and Realtime options to understand what I'm doing, I'm missing simple examples here.
I've downloaded the ZIP and used SCP to transfer the www directory.
I still have one problem because I'm using 3 FLM's on different locations and because of that I have to do some port forwarding.
On a remote location I don't get anything visual, is there another port to open except port 80 ?
Thanks for all the work, this was what I was waiting for.
Kind regards and a very good 2017 for all the co-workers on the project.
Robert (France).
gebhardm |
Hello Robert,
thanks a lot; also to you a wonderful start into 2017; may it be less weird than 2016, especially for you in France (and all the Belgian Fluksonians)...
With respect to your question: That is a rather tricky one as I must admit that I did not use the visualizations remotely, but within a LAN only... The visualizations use the Fluksometer built in webserver that reports on port 80; the mqtt websocket connection therein uses port 8083 to gain access to the mosquitto broker (see for example https://github.com/gebhardm/flmlocal/blob/master/www/scripts/controllers...) - so what happens is: You call the webserver which establishes by script a connection to the mqtt broker of the Fluksometer it runs on. So far, so good - or bad. This broker connection is established to the "localhost" address, which is in the local network of the respective Fluksometer. This may be the actual hurdle to take, as port forwarding does not work if the address does not correspond... So, try first forwarding port 8083. If this does not work out, then you have to take a look at the address part (and maybe use a reverse proxy like nginx if you do not want to put your Fluksometer into a DMZ, which I would not do). For want of an example I would also have to try out, but actually lack need ;-)
Hope that provides at least an idea (the nginx part I tried and routing therein is rather promising).
Best regards
Markus
gebhardm |
Robert - speaking of "realtime" you use an FLM03, don't you? If so, please keep this thread to the FLM02/v250 issue and open a respective thread in the Dev Corner. And note again FLM02 and FLM03 share a visualization base, but have forked on April 08, 2016 as they have some incompatible differences - https://github.com/gebhardm/flmlocal/network
rs |
No Markus, all three are FLM2 with FW 250 but your guess about port 8083 was the right one although the refressing-time is 25-26 sec. instead of 1 sec.
Apparently it takes a detour by the browser.
Another problem also, because I didn't found the correct syntax I've changed the password at the local one but something went wrong, can I get in or is there another way to recover ?
Robert.
rs |
I also don't have the network or port configuration anymore after starting the demon, a blank screen apears.
rs |
Update: I do come in the lan interface with the changed password but not anymore with SCP or SSH (Putty)
vk2him |
Hi RS and Markus,
As an experiment with the right combination of port-forwards I can confirm correctly working access to visualisations remotely with updates every second.
I have a public webserver running on my network so port 80 on the WAN side isn't available to use to view the visualisations, so I portforwarded 8080 on the WAN side to port 80 on the Flukso's LAN IP. I also portforwarded Port 8083 WAN to the Flukso's LAN IP port 8083.
I was then able to navigate to http://www.mysite.com:8080 and select the visualisations from the drop-down selectors. Note: - I strongly recommend changing your root password from default since now your flukso login menu is available via public internet.
rs |
All the best for 2017 also Ian !
Of course I'm using another portnumber also for the FLM but my router is in stealth mode so a portscan returns nothing (shieldsup at grc.com) but anyway changing the pasword into a difficult one is always the best.
I also do have a webserver with QSL running on port 80.
I don't know why my updates tooks so long (26 sec), maybe because I'm using a nat after a nat, have to try it. Opening port 8083 to my computer doesn't change anything.
I've restarted the local FLM but I still cannot login with SCP or Putty with the old or changed password.
However I can login via it's IP with the browser, I do get the Status information but the port and network configuration does nothing anymore.
Robert.
gebhardm |
What is the error message on login fail? There is no difference in the passwords for web and SSH.
gebhardm |
With respect to port forwarding - if it is remote Fluksometers: Do you forward port 22 also? This is what my FLM02 reports in nmap:
Starting Nmap 6.46 (<a href="http://nmap.org"title="http://nmap.org">http://nmap.org</a>) at 2017-01-02 14:07 CET
Nmap scan report for<FLM ip>
Host is up (0.42s latency).
Not shown: 995 closed ports
PORT STATE SERVICE
22/tcp open ssh
53/tcp open domain
80/tcp open http
8080/tcp open http-proxy
8083/tcp open us-srv
rs |
Yes, of course I've forwarded port 22 also, but I have the login problems on the local FLM at the same network, the message is simplement 'access denied'.
I tried on the ethernet interface but with the same results, I am returned to the wifi interface but now I can't come in at all. He's present, has his IP-address, is working on Flukso.net but not responding on his HTTP-server.
At the remote I also do not have the configuration options anymore, I updated the www for the visualisations only.
Hello VK2HIM, you should upgrade to v250 as it brings much more stability (my FLM02 didn't have an issue for a very very long time now); yes, then you have to reload the visualizations. Please be aware that I synced on FLM03, so there is a special branch/release for the v2 FLM visualizations now --> https://github.com/gebhardm/flmlocal/releases
Release notes are here --> https://www.flukso.net/content/v250-changelog
Best regards, merry christmas and a happy new year...
Markus
Thank you for the information Markus - I'll update in the next day and reload the visualisations - Merry Christmas and Happy New Year to you too!
...and try out the chart functionality with the corresponding flukso.init change :-)
TMPO is really a cool feature as you have real history data by that...
https://github.com/gebhardm/flmlocal/tree/flm02#tmpo-query-daemon
Hi Markus,
I upgraded to v250 and reloaded visualisations plus chart functionality is working great - thanks!
I found one issue when following your instructions - during the scp the flm runs out of space because when cloning "git clone http://github.com/gebhardm/flmlocal", the downloaded www directory also contains a directory called "flmlocal" - this shouldn't exist. When you scp the local www directory it runs out of space when it gets to www/flmlocal. To fix, I deleted the flm's /www/flmlocal/ to free the space (rm -r /www/flmlocal) and then scp again after deleting the /www/flmlocal directory on my local disk.
Thanks again!
P.S. - maybe the extra flmlocal directory in www was my mistake as I can see that there is no flmlocal directory when manually looking at https://github.com/gebhardm/flmlocal ... I'd say I accidentally copied it twice :( All good now though :)
git is full of wonders :-) I guess you cloned a second time while already being in a locally cloned flmlocal/www directory. If so, a
git pullwould have brought the latest version; mind the different flavors/branches for flm02 and flm03...Hi Markus,
This is really very good news, using Mosquitto to the FLM on a RPI was too complicated for me but your flmlocal implementation works wonderfull.
I have to study on the Graph and Realtime options to understand what I'm doing, I'm missing simple examples here.
I've downloaded the ZIP and used SCP to transfer the www directory.
I still have one problem because I'm using 3 FLM's on different locations and because of that I have to do some port forwarding.
On a remote location I don't get anything visual, is there another port to open except port 80 ?
Thanks for all the work, this was what I was waiting for.
Kind regards and a very good 2017 for all the co-workers on the project.
Robert (France).
Hello Robert,
thanks a lot; also to you a wonderful start into 2017; may it be less weird than 2016, especially for you in France (and all the Belgian Fluksonians)...
With respect to your question: That is a rather tricky one as I must admit that I did not use the visualizations remotely, but within a LAN only... The visualizations use the Fluksometer built in webserver that reports on port 80; the mqtt websocket connection therein uses port 8083 to gain access to the mosquitto broker (see for example https://github.com/gebhardm/flmlocal/blob/master/www/scripts/controllers...) - so what happens is: You call the webserver which establishes by script a connection to the mqtt broker of the Fluksometer it runs on. So far, so good - or bad. This broker connection is established to the "localhost" address, which is in the local network of the respective Fluksometer. This may be the actual hurdle to take, as port forwarding does not work if the address does not correspond... So, try first forwarding port 8083. If this does not work out, then you have to take a look at the address part (and maybe use a reverse proxy like nginx if you do not want to put your Fluksometer into a DMZ, which I would not do). For want of an example I would also have to try out, but actually lack need ;-)
Hope that provides at least an idea (the nginx part I tried and routing therein is rather promising).
Best regards
Markus
Robert - speaking of "realtime" you use an FLM03, don't you? If so, please keep this thread to the FLM02/v250 issue and open a respective thread in the Dev Corner. And note again FLM02 and FLM03 share a visualization base, but have forked on April 08, 2016 as they have some incompatible differences - https://github.com/gebhardm/flmlocal/network
No Markus, all three are FLM2 with FW 250 but your guess about port 8083 was the right one although the refressing-time is 25-26 sec. instead of 1 sec.
Apparently it takes a detour by the browser.
Another problem also, because I didn't found the correct syntax I've changed the password at the local one but something went wrong, can I get in or is there another way to recover ?
Robert.
I also don't have the network or port configuration anymore after starting the demon, a blank screen apears.
Update: I do come in the lan interface with the changed password but not anymore with SCP or SSH (Putty)
Hi RS and Markus,
As an experiment with the right combination of port-forwards I can confirm correctly working access to visualisations remotely with updates every second.
I have a public webserver running on my network so port 80 on the WAN side isn't available to use to view the visualisations, so I portforwarded 8080 on the WAN side to port 80 on the Flukso's LAN IP. I also portforwarded Port 8083 WAN to the Flukso's LAN IP port 8083.
I was then able to navigate to http://www.mysite.com:8080 and select the visualisations from the drop-down selectors. Note: - I strongly recommend changing your root password from default since now your flukso login menu is available via public internet.
All the best for 2017 also Ian !
Of course I'm using another portnumber also for the FLM but my router is in stealth mode so a portscan returns nothing (shieldsup at grc.com) but anyway changing the pasword into a difficult one is always the best.
I also do have a webserver with QSL running on port 80.
I don't know why my updates tooks so long (26 sec), maybe because I'm using a nat after a nat, have to try it. Opening port 8083 to my computer doesn't change anything.
I've restarted the local FLM but I still cannot login with SCP or Putty with the old or changed password.
However I can login via it's IP with the browser, I do get the Status information but the port and network configuration does nothing anymore.
Robert.
What is the error message on login fail? There is no difference in the passwords for web and SSH.
With respect to port forwarding - if it is remote Fluksometers: Do you forward port 22 also? This is what my FLM02 reports in nmap:
Yes, of course I've forwarded port 22 also, but I have the login problems on the local FLM at the same network, the message is simplement 'access denied'.
I tried on the ethernet interface but with the same results, I am returned to the wifi interface but now I can't come in at all. He's present, has his IP-address, is working on Flukso.net but not responding on his HTTP-server.
At the remote I also do not have the configuration options anymore, I updated the www for the visualisations only.
This year is not starting very well I supose.
Robert