Data Source Permissions after import?

dan

Hey Guys, I've had a major issue with one of my setups where I had trouble with the SSL cert expiring and not renewing, after days of mucking around I've finally gotten it to work again, but in the process I reinstalled mango about 4 times.

A side effect of this process seems to have somehow buggered up permissions on my data sources / points and on the dashboard. Everything is just greyed out with the red crosses. I've checked view permissions etc on each user but this is even doing it for the admin accounts.

I've tried going into a point on the dashboard and clearing the XID value, then selecting it from the dropdown box, but it just comes back as greyed out again.

I've also tried re-applying permissions throughout the data sources and data points themselves, to no avail.

Is there something I'm maybe missing between doing a configuration export then import into a new instance?

I can't see anything obvious in the logs. :(

Any ideas would be greatly appreciated.

Cheers
Dan

cbyrne

@dan Any chance it might actually be a websocket proxy issue? It can cause similar results from experience.

dan

@cbyrne maybe? I do have a proxy setup for SSL redirect.
I'll check the console and see if it has anything in there.

cbyrne

@dan Quick way to check is your browser's dev tools. In Firefox, if you right click and select inspect and then go to the console tab you'll see error messages along the lines of "couldn't connect to ws://your.domain". I presume it's similar in chrome dev tools.

dan

@cbyrne yeh definitely getting those errors. :(
I'll have to work out why the proxy redirect isn't working as intended.

cbyrne

@dan Well at lease we know what it is! What's your proxy server?

dan

@cbyrne thanks for the help with this.
It's apache2 with an SSL cert as I couldn't for the life of me get it to renew correctly on Mango itself.
That side of it appears to work, the GUI loads seemingly normally.
Just the data sources have that ws:// error. Have I maybe not enabled something correctly for the proxyredirect to work.

cbyrne

@dan Here's my apache config, hopefully you can get yours working from it

<VirtualHost *:80>
    ProxyRequests Off
    ProxyPreserveHost On

    Redirect permanent / https://your.domain/
</VirtualHost>

<VirtualHost *:443>
    ServerName your.domain
    ServerAlias your.domain

    ErrorLog "/var/log/your.domain_error.log"
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn
    CustomLog "/var/log/your.domain_access.log" combined

    SSLEngine On
    SSLProxyEngine On
    ProxyRequests Off
    ProxyPreserveHost On

    # allow for upgrading to websockets
    RewriteEngine on
    RewriteCond %{HTTP:Connection} Upgrade [NC]
    RewriteCond %{HTTP:Upgrade} websocket [NC]
    RewriteRule /(.*) ws://127.0.0.1:8080/$1 [P,L]

    RequestHeader set Origin "http://your.domain"
    Header edit Location ^http://your.domain https://your.domain

    <Location />
        ProxyPass http://127.0.0.1:8080/
        ProxyPassReverse /
    </Location>

    SSLCertificateFile "/etc/httpd/conf.d/ssl/your.domain.crt"
    SSLCertificateKeyFile "/etc/httpd/conf.d/ssl/your.domain-pkey.pem"
</VirtualHost>

dan

@cbyrne thanks for that.

I don't have this line:

<Location />
    ProxyPass http://127.0.0.1:8080/
    ProxyPassReverse /
</Location>

The other references to localhost in that config file are pointing to the machine's eth IP. Wonder if I should change them to localhost?
A lot of them refer to :443 for the SSL too, Mango itself is running on :8080

I think I'm confusing myself with how the redirect proxy works.

dan

@cbyrne I used this reference in the Mango docs..

https://docs-v4.mango-os.com/proxy

There is a note at the bottom referring to v3.7.0+ and I'm running latest 4.2.3. Where would I change this stuff? mango.properties?

dan

@cbyrne I deleted the version I had that was made from the Mango docs template and used yours instead and it worked!

Thanks heaps for your help.

Where do I send beer?

Cheers
Dan

cbyrne

@dan don't mention it! Happy to help. I actually omitted one or two things from that config for brevity. I'll edit it now, just some logging you might want to add.

dan

@cbyrne Well thank you that is very kind of you, now it's working great.

Cheers
Dan