Jump to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Is this my local 3g or is it me?

Featured Replies

Posted

I can access my ISY from remote via web no problem. https:\\70.67.xxx.xxx:801 with a port forward in my router to port 192.168.xxx.xxx:443 where my ISY resides. For testing purposes I've also set up a port forward to port 80 so that http:\\70.67.xxx.xxx:806 forwards to 192.168.xxx.xxx:80. Both of these forwards work fine from any PC based web browser.

 

For some reason, though, if I try to browse to that from my blackberry or from my buddy's iphone I get a gateway error. I can't connect from either of these devices.

 

I don't have the iphone in my hands but the error on the bb is 'the selected server returned an error when attempting to fulfill your request'. Sometimes I get the message 'Gateway Timeout - The gateway timed out while waiting for a response from the server. Please try loading a different page'. If I ask for details of the message it tells me that the connection failed and that the system returned 'connection refused'

 

I've telnetted in to the ISY and upped both the HTTP and HTTPS timeouts to max - 50,000ms. No difference. I've enabled and disabled java support on the bb browser (I saw something about this in another post) but no difference.

 

Could this just be crappy 3g performance in my area? Or is there something else I'm missing?

 

Thanks,

 

mark

It could be. Have you tried different ports? Perhaps your carrier is blocking ports 801 and/or 806.

  • Author
It could be. Have you tried different ports? Perhaps your carrier is blocking ports 801 and/or 806.

 

Good one, Brad!

 

I changed to use the standard port 80 redirected to the non-secure ISY port on 80 and it got in right away.

 

Then I tried forwarding 80 to the secure port on 443 via an http request (not https) and got the same error as before

 

Next I tried forwarding 80 to 443 using an https request and that worked fine.

 

Finally I tried external 443 to internal 443. http request doesn't work - https request does.

 

So it seems that

a) my carrier is blocking non-standard ports but 80 and 443 work fine.

B) my bb browser won't forward an http request to an https server

 

Thanks for the direction, Brad!

 

mark

You can't use http and https interchangeably. If you are connecting to your ISY's non-secure port, you must use http. If you are connecting to your ISY's SSL port, you must use https. There's no getting around that.

 

If you make a non-SSL http request to the SSL https port, your ISY will reject that request. It's not your Blackberry's fault.

 

HTTP and HTTPS don't just specify ports. They are URI schemes that tell the browser (client) and the server how to connect. When you connect to 443 using http you are getting the port right, but the URI scheme wrong.

 

Also, your carrier might not be blocking all "non-standard" ports. It may just be using those ports or reserving them for something else. If you wish to use something other than 80 or 443, I recommend using a port higher than 1024 and lower than 49152.

 

For example, if you used 1780 for http and 1783 for https, you'd address them like this:

 

http://yourip:1780

https://yourip:1783

 

Lastly, I would recommend that you only use the SSL when connecting from outside your home. Connecting via http will send your username and password in the clear, which could be intercepted by someone sniffing your traffic.

  • Author

The http to https thing was what was messing me up. I've done lots with http but nothing with https. I'd assumed that if I browsed to a secure site via http it would refer me automagically to the https version but as I see now that's apparently not so.

 

My carrier blocking non-standard ports is interesting too.... I'll have to contact them and find out if they block all or leave some for folks like us who port forward in to many different devices.

The http to https thing was what was messing me up. I've done lots with http but nothing with https. I'd assumed that if I browsed to a secure site via http it would refer me automagically to the https version but as I see now that's apparently not so.

That's right. Many sites on the 'net will redirect you to https when necessary so that it's transparent to you, which is probably why you've never noticed it before.

  • 3 years later...

If you make a non-SSL http request to the SSL https port, your ISY will reject that request. It's not your Blackberry's fault.

 

HTTP and HTTPS don't just specify ports. They are URI schemes that tell the browser (client) and the server how to connect. When you connect to 443 using http you are getting the port right, but the URI scheme wrong.

 

Also, your carrier might not be blocking all "non-standard" ports. It may just be using those ports or reserving them for something else. If you wish to use something other than 80 or 443, I recommend using a port higher than 1024 and lower than 49152.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.