Topic: Meteobridge Forgot Me?

[Bushman]

Keep getting this:  " Acceptance of license terms is a prerequisite for using this application".  Every time I log in remotely.

[lrosenman]

Did you check the accept box on the license page LOCALLY, and have you bought a real license after the (30? day) trial?

[Bushman]

I have had the license for a couple years.  BUT it seems like accessing it locally did the trick.  Thanks for the help!

[SpringHillWeather]

Keep getting this:  " Acceptance of license terms is a prerequisite for using this application".  Every time I log in remotely.

Are you having this issue?

http://www.wxforum.net/index.php?topic=29321.msg287552#msg287552

[Bushman]

Yeah, I knew I saw that somewhere!  Hard to find with the terse thread title.  And yes, the IP did change - got a new router.  The local lo-in (using the new IP via the new router) and then accepting the license again fixed it.  The explanation in the thread makes sense.

[docbee]

Most routers provide the feature to give a unit receiving an IP address via DHCP a fixed IP. This is the preferred way to avoid changing IPs of certain devices in the LAN and to also keep it working when the router changes and the new router defines a new class C network. When you have the IP statically set inside the Meteobridge, then it will fail in the "router changes" situation. When the Meteobridge stays at DHCP it will instantly work in the new setup, but of course it will need you to find the new IP it received from the new router.

Doing so will give you best of both worlds: Fixed IP but also flexibility to have it instantly working in new DHCP setups.

[Bushman]

Static works better for me since I can port forward to it, without the secret URL.

[Mattk]

Also use static which works well with remote access, DNS and port forwarding as well as remote SMB access. Hopefully in due course Doc will provide a user configurable port number apart from the current/default/standard port 80

[SpringHillWeather]

I use static too but just realized I made a boo boo when I forgot to use the proper range for static IP on my router.

According to Verizon Fios you must use ranges above 192.168.1.100 for static IP's.   I had servers setup this way but forgot recently and did have my meteobridge set on the low IP.  I noticed while adding my PI that the verizon router showed lease expired on my devices which made me realize my mistake. 

I now set all my weather devices to .110 -> and servers at .200 -> all has been well.

[docbee]

Also use static which works well with remote access, DNS and port forwarding as well as remote SMB access. Hopefully in due course Doc will provide a user configurable port number apart from the current/default/standard port 80

Is that still an urgent request? Most user configure their router when setting up port forwarding to also translate the port to something different on WAN side. By that you can reach many devices in your LAN on port 80 from the outside.

This is the much better way, because my experience is that users tend to define a different HTTP port, don't really understand the impact or forget about it later on and by that add to the self-inducted support requests popping up on my side 

This is what keeps me being reluctant to implement this feature.

[Mattk]

No it's not urgent as there are ways around it. There is the Admin server link which basically does the same job as forwarding port 80 to the MBPro itself but if Port 80 is forwarded to the Pro then it's simple enough to delete and re-forward to say the WLIP if one needs access to the logger page, which in most cases is really not all that common.