My Portal is not coming up.

Related to the Portal
User avatar
Posts: 1833
Joined: Sun Apr 21, 2013 6:25 am
Location: Davie, FL
PostPosted: Mon Jul 20, 2015 2:32 pm
It seems my IP address has changed, but even with that the Portal is not displaying the correct.
It shows an IP address of 72.145.32.187, but it is currently 65.3.128.xxx

I can pull up the r99 with either my internal IP address or the new 65.3 address.

Doesn't the Portal get the IP address from the WiFi module directly and should update when the IP address changes?

I can understand there being a delay with the DNS name updating, but the actual IP address on the Portal?

Posts: 250
Joined: Wed Jan 28, 2015 5:17 pm
PostPosted: Mon Jul 20, 2015 5:46 pm
I don't know if this is related or not but my portal says unreachable address and I can't access the controller through the app. All was working fine until about a couple of days ago.
Image
User avatar
Posts: 1833
Joined: Sun Apr 21, 2013 6:25 am
Location: Davie, FL
PostPosted: Wed Jul 22, 2015 5:11 pm
It happened again today at around 3:30pm, because the last time my phone connected was 3:28pm.
My current ip address is 65.4.160.xxx but the portal shows the ip address as 65.3.128.235.

Posts: 12188
Joined: Fri Mar 18, 2011 6:47 pm
PostPosted: Thu Jul 23, 2015 7:51 pm
It seems data is updating again. Did you do anything?
Roberto.
User avatar
Posts: 1833
Joined: Sun Apr 21, 2013 6:25 am
Location: Davie, FL
PostPosted: Fri Jul 24, 2015 3:40 am
No. I've done nothing.
The app I changed from console to portal and it updated or even away to home would work sometimes, but the portal was still down.
User avatar
Posts: 1833
Joined: Sun Apr 21, 2013 6:25 am
Location: Davie, FL
PostPosted: Sat Aug 15, 2015 6:59 am
It;s happening again.
My IP address changed this morning when I re-booted my router to 74.161.16.XXX and the portal is still showing the old IP of 65.6.0.115.

I can't get anything though.
The App works and the internal server comes up with 74.161.16.XX:2000/r99, but the portal still has the wrong IP address.

I tried rebooting the head unit and no difference.

Posts: 12188
Joined: Fri Mar 18, 2011 6:47 pm
PostPosted: Mon Aug 17, 2015 8:53 am
It seems it is normal again.
I think it just takes some time when you are using DDNS.
Let me see if I can find any bug with the DDNS update.
Roberto.
User avatar
Posts: 1833
Joined: Sun Apr 21, 2013 6:25 am
Location: Davie, FL
PostPosted: Mon Aug 17, 2015 9:19 am
Yes it does resolve itself eventually, but it can take up to a day to do so.
Isn't the Portal supposed to get the ip address directly from the WiFi Unit or head unit?
So the DDNS should have nothing to do with it.

Posts: 12188
Joined: Fri Mar 18, 2011 6:47 pm
PostPosted: Mon Aug 17, 2015 10:03 am
I need to look at the code, but the DDNS update has priority over the ip address.
So, when the request is sent to the server, which includes both ip and DDNS, the server tries to update the DDNS first.
It fails and quits and it never updates the ip.
That's what I'm thinking it is happening.
Roberto.
User avatar
Posts: 1833
Joined: Sun Apr 21, 2013 6:25 am
Location: Davie, FL
PostPosted: Mon Aug 17, 2015 10:06 am
Ok. Thanks.
Next

Return to Portal

Who is online

Users browsing this forum: No registered users and 1 guest