Viewing 25 posts - 26 through 50 (of 60 total)
  • Author
    Posts
  • #36347

    Samer
    Keymaster

    The white screen was caused by an incorrect URL. The correct beta UI URL is: https://betaui.opensprinkler.com/js.

    Furthermore, this issue was resolved without the need for using the beta. The underlying issue was FireFox complaining of a weak self-signed certificate. The secondary issue was the Javascript URL used by OpenSprinkler was non-secure by default and caused an issue when the primary site being accessed is using SSL.

    Thanks

    #36360

    aruzsi
    Participant

    Can you help me again?

    I changed the ssl.pem file (I want different cert for different name based virtual servers) in my lighttpd and I can’t “login” as yesterday. Browser: Firefox.

    The Script URL went back to: https://ui.openspinkler.com/js. I don’t know why.

    #36363

    aruzsi
    Participant

    I changed the Script URL to https://betaui.openspinkler.com/js and after login and Loading I got: 500 Internal server error.

    I created a new cert with RSA 2048 bit and SHA-256. Is that the problem?

    #36364

    aruzsi
    Participant

    I think the problem is the Firefox. Chrome is working. Opera is like Firefox. 🙁

    #36366

    Samer
    Keymaster

    Right, those are the same symptoms as yesterday. Like we discussed, it is your SSL certificate that is using a weaker SHA-1 algorithm causing FireFox and Opera to reject the certificate. If you say your using SHA-256 now, then you should post any error messages you are getting from FireFox console here.

    Also, you don’t need to use betaui as the issue is unrelated. Therefore, you can continue using: https://ui.opensprinkler.com/js.

    Thanks

    #36367

    aruzsi
    Participant

    As I mentioned I recreate my certs with RAS:2408 bit and SHA-256.

    #36368

    Samer
    Keymaster

    As I said in my previous message, paste your error here please.

    Please do try to provide as much information otherwise this thread can grow to 100 pages without any resolution.

    #36369

    aruzsi
    Participant

    Something happened with the hardware because I got 500 Internal server error in Chrome, too and no ping answer. 🙁

    #36370

    Samer
    Keymaster

    Internal error 500 means your Proxy is failing because OpenSprinkler will not return a 500 error code.

    #36371

    aruzsi
    Participant

    l can’t reach the spinkler from internal address.

    Ű
    Ű

    #36372

    Samer
    Keymaster

    Again, can you please provide details? What is the error? etc.

    #36377

    Ray
    Keymaster

    What does this mean:
    Ű
    Ű
    is this what your browser returns, or what’s displayed on the LCD screen, or something else? Can you go to OpenSprinkler, click a button, like B1, and see if the LCD responds with the IP address?

    #36378

    aruzsi
    Participant

    I don’t know what was the problem.

    On the LCD above the field strength simbol there was an X signal.

    I power down and up the spinkler and the X disappeared.

    Something happened with the network because the lost packets are high.

    #36379

    aruzsi
    Participant

    I can see the IP address if I push the B1 button.

    I don’t know what does it mean an arrow in the last character in the 2nd line. Sometime it appears for some seconds.

    #36380

    aruzsi
    Participant

    Here it is the output from the Firefox console:

    A vegyes aktív „http://locsolo.info.tm/jp?pw=*REMOVED*” tartalom betöltése blokkolva[További információ] app.jgz:8:0

    It was repeated 5 times.

    #36382

    Samer
    Keymaster

    This error means you didn’t mark SSL on the site manager page for the device.

    #36383

    aruzsi
    Participant
    #36384

    aruzsi
    Participant

    I changed to https://betaui.openspinkler.com/js and it is working.

    #37041

    aruzsi
    Participant

    Hi,

    Can you help me again as some weeks ago?

    Little bit different behaviour between Firefox and Chrome.

    My HTTPS front-end doesn’t work correctly.

    I don’t know the correct setup for internal (it is clear), external with port forwarding (not secure!) and external with SSL front-end.

    WEB vs. app.

     

    I don’t want to connect my sprinkler system from the Net without SSL. So I don’t understand many things.

    Can you help me?

     

    TIA,

    #37042

    Samer
    Keymaster

    OpenSprinkler does not support SSL out of the box however the app supports SSL and Basic Auth if you use a reverse proxy. We don’t have an official guide as the setup can be quite variable based on the setup at home.

    Basically, if you want to securely open access to OpenSprinkler: you need to have a web server installed such as Apache and proxy pass the path to the OpenSprinkler from there.

    #37043

    aruzsi
    Participant

    OK.

    What do I have to config if I want to use the SSL option in app?

    I have got a router with lighttpd as proxy. Doesn’t work perfectly. I don’t know why. For example the weather diagnostic always complains about time out.

    There are many Network failure but from the internal connection everything is working. So I don’t understand.

    TIA,

    #37044

    aruzsi
    Participant

    If you give me an e-mail I can send you my setup (lighttpd.conf, etc.)

    TIA,

    #37045

    Samer
    Keymaster

    The Weather Diagnostic popup does not talk to OpenSprinkler but rather polls Weather Underground. Therefore, this is an unrelated issue and suggests something else entirely.

    Which app are you using?

    This is considered an advanced topic and not something we have a guide for and is left for the user who is capable of performing such a task. Don’t get me wrong, I don’t think this is ideal and we are working on a solution to avoid port forwarding and having to use SSL proxies to ensure security.

    Also, I have never used lighthttp so sending me the config really won’t help much.

    #37046

    aruzsi
    Participant

    OK.

    Android app. No info what the app do if my “sprinkler page” (SSL frontend) is want HTTPS and different port.

    I use name based virtual hosts for proxy.

    I thought the secured connection is a must. I tried to help you test it. I don’t know your js or app how works. Of course I can watch it as a black box and I can use tcpdump to check the protocols both of the two side of the router.

    I know you don’t have too much time.

    Anyway, do you interested in this type of setup (SSL frontend with proxy)?

    TIA,

    #37047

    Samer
    Keymaster

    Sorry I don’t quite understand however I will say I use this every single day. My personal setup uses Apache proxy and it works even better than directly accessing the controller remotely since Apache is a much more capable web server than the Arduino based server.

    So yes, this works fine on my setup. I recommended making a new site instead of changing a current one to use SSL, if you are using the app.

Viewing 25 posts - 26 through 50 (of 60 total)
  • You must be logged in to reply to this topic.