Personal web site is visible but mango management is not visible

etantonio

Hy,
I can't understand why on some pc (for example actually on ubuntu 18.04) Mango automation correctly show my site

ptth://ip:port/user-dashboards/solergy

but it is not possible to show the management consolle

ptth://ip:port/

maybe a security problem?
Thanks

Antonio

phildunlap

Hi Antonio,

Please do not post links to your server. If you're not a security problem in providing an opaque link, it is a security problem for you to let the world know where your server is.

I suggest you keep your browser's development console open when you're investigating the issue. I'm not sure what you're referring to with 'management console'. Do you just mean the Mango interface? If so it could suggest perhaps yes there is some kind of proxy in the way, but I'm not certain that's definite - especially considering you posted an IP (which I did not attempt to visit).

It would be good to know if the request for just the IP and port is timing out or getting rejected. Is your dashboard public and doesn't require a login?

etantonio

Yes, I'm talking about the mango interface where I can manage datasource and other things.
Normally to see this dashboard login is required, it happens on another server.
I think it is not a timeout because the page remains blank and the answer is immediately

phildunlap

Can you try requesting the /ui/login URL directly? Maybe there is some issue with redirecting. You could try clearing your browser cache and the cookies for that host, too.

Edit: Having seen your other post, if this is 2.8.x you would want to try to navigate to /login.htm directly.

etantonio

using chrome instead of firefox the answer to
/login.htm
is more clear
HTTP ERROR 500
but the error is not in the ma.log file

phildunlap

Definitely try launching Mango on the command line then, so that we can see if the message is getting to stderr. You said it's ubuntu so this means cd Mango/bin; ./ma.sh start

You could try deleting your Mango/work directory, but I would have expected an error caused by that to be logged.

etantonio

I'm sorry,
no answer in the starting console after calling /login.htm
the same result also after deleting the work directory

phildunlap

Hmm...

I would try,

Requesting the page with the developer tools open, on the network tab, to see if there is any information in the 500 response

With Mango stopped, move your Mango/databases directory somewhere for safe keeping. Then start Mango on a fresh database. Do you still have this issue?

If this is the same instance as in the other thread where the manual upgrade went awry, then you should resolve the duplicate jar situation before troubleshooting this as having multiple versions of the jar files could produce a variety of runtime exceptions.

But, I really would have expected some output to stderr or stdout from a 500 exception. There are no errors in your log file?

etantonio

It seems no header available, just a @Game over@

phildunlap

Try Chrome. You can check the "Preserve log" checkbox (see my screenshot) and it will definitely keep the request in view of the network tab. You have to have the developer tools open before you request the page.

etantonio

This is the result

phildunlap

@phildunlap said

But, I really would have expected some output to stderr or stdout from a 500 exception. There are no errors in your log file?

Have you checked your Mango/logs/ma.log or perhaps Mango/bin/logs/ma.log file?

What does the response tab display? Please copy the whole content of the request and the response, rather than a cropped image.

etantonio

Hy,
in ma.log there's nothing concerning this request.
following there's all coming from network tab of Chrome developer network tool,
thanks for your help,
Antonio

Request URL:http://xxxx:yyyy/
Request Method:GET
Status Code:500 Server Error
Remote Address:xxxx:yyyy
Response Headers
view parsed
HTTP/1.1 500 Server Error
Date: Thu, 27 Sep 2018 16:17:16 GMT
Connection: close
Request Headers
view parsed
GET / HTTP/1.1
Host: xxxx:yyyy
Connection: keep-alive
Cache-Control: max-age=0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,/;q=0.8
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36
Accept-Encoding: gzip, deflate, sdch
Accept-Language: it-IT,it;q=0.8,en-US;q=0.6,en;q=0.4
Cookie: XSRF-TOKEN=94a6236e-1520-43c4-b399-f59c2801c8a7; MANGO8800=jhmtbh78rpo2pc2zrb31aift

phildunlap

The 500 error would be in your log. If not, you can try launching at the command line (navigate to the Mango/bin directory and start with either ./ma.sh start or ma-start.bat and try to load the page again. If that 500 error is from Mango, there absolutely will be some output.

With nothing but an unknown 500 error, my advise would be to attempt reinstalling and to ensure you are not accessing over a proxy. There is very likely some error output.

etantonio

it is really strange,
for example if instead of http://server:port/login.htm
is required the page http://server:port/data_point_details.shtm

in ma.log I've just the log:

WARN 2018-10-02 15:14:32,049 (com.serotonin.m2m2.web.filter.UrlSecurityFilter.doFilter:95) - Denying access to page where user isn't logged in, uri=/data_point_details.shtm, remote host ip= 95.243.234.182
WARN 2018-10-02 15:14:32,050 (com.serotonin.m2m2.web.filter.LoggedInFilter.doFilter:55) - Denying access to secure page for session id 13gvqk69w3vpso64apcqdpzpy, uri=/data_point_details.shtm

On the ubuntu virtual desktop 18.04 I've nothing neither in syslog or ufw.log

If I request the url during mango startup this is the result

Any other idea?

And also, there's a way to bypass the problem considering that

http://server:port/user-dashboards/solergy/login

is working fine?

Thanks
Antonio

phildunlap

I keep asking about proxies. Like, were it behind Apache...

And also, there's a way to bypass the problem considering that

Yes, you can make Graphical Views public or dashboards in the old Dashboards module, and you could make a proxy only forward a subset of urls.

If you were launched at the command line, had no proxy in the way, and received a 500 response in 2.8.4, I will not believe nothing is logged until I see it, and wouldn't look until I am confident you have attempted my suggestions, such as starting a clean installation on a clean database (but I've never seen any sort of corruption there cause what you're describing, and certainly not without logs).

etantonio

Finally problem solved, naturally it was due to my mistake,
installed on Ubuntu 18.04 openjdk instead of jre1.8, and, it seems, but is not the same thing.
Thanks for your help.
Antonio

phildunlap

Still weird to me that wouldn't produce errors if you launched at the command line!

Thanks for sharing the resolution.