cannot access sormas domain

SORMAS-Foundation / SORMAS-Project

SORMAS (Surveillance, Outbreak Response Management and Analysis System) is an early warning and management system to fight the spread of infectious diseases.

https://sormas.org

GNU General Public License v3.0

293 stars 143 forks source link

cannot access sormas domain #2056

Open RafaelKluender opened 4 years ago

RafaelKluender commented 4 years ago

I have successfully run the server-configuration and server-update scripts. No errors popped up, finally. But I still cannot access the domain from the internet. when I type IP:6080/sormas-ui/login I get a connection reset.

I have started the service payara-sormas, and when I check the domain using: curl http://127.0.0.1:6080/sormas-ui/login

I get:

<!doctype html>

What is the problem here?

MateStrysewske commented 4 years ago

Which URL exactly did you use in your browser? It should be localhost:6080/sormas-ui/login if it's a local server that you're running on the same system that you try to access it on.

RafaelKluender commented 4 years ago

I have no browser on the server installed. I do get an answer via the curl command though: curl http://127.0.0.1:6080/sormas-ui answers: This document has moved <a href="http://127.0.0.1:6080/sormas-ui/">here</a>.<p>

So it's seems to work. Yet, from the outside payara seems to refuse connections.

MateStrysewske commented 4 years ago

Have you also set up the Apache web server?

RafaelKluender commented 4 years ago

I just ran a portscan, 6080 is actually closed, despite the fact that I enabled it on the firewall. It only works from localhost. I must check why 6080 is closed and I'll come back to you.

RafaelKluender commented 4 years ago

When I run: sudo lsof -i -P -n | grep LISTEN

I see that payara is only listening to localhost:

systemd-r 606 systemd-resolve 13u IPv4 17740 0t0 TCP 127.0.0.53:53 (LISTEN)
apache2 727 root 4u IPv6 20578 0t0 TCP *:80 (LISTEN)
apache2 728 www-data 4u IPv6 20578 0t0 TCP *:80 (LISTEN)
apache2 729 www-data 4u IPv6 20578 0t0 TCP *:80 (LISTEN)
sshd 734 root 3u IPv4 20004 0t0 TCP *:22 (LISTEN)
sshd 734 root 4u IPv6 20015 0t0 TCP *:22 (LISTEN)
postgres 844 postgres 3u IPv4 21178 0t0 TCP 127.0.0.1:5432 (LISTEN)
java 939 payara 456u IPv6 22131 0t0 TCP 127.0.0.1:6080 (LISTEN)
java 939 payara 529u IPv6 22953 0t0 TCP 127.0.0.1:6048 (LISTEN)
java 939 payara 544u IPv6 22134 0t0 TCP 127.0.0.1:6037 (LISTEN)
java 939 payara 609u IPv6 22993 0t0 TCP 127.0.0.1:6038 (LISTEN)
java 939 payara 621u IPv6 22994 0t0 TCP 127.0.0.1:6039 (LISTEN)
java 939 payara 646u IPv6 22243 0t0 TCP 127.0.0.1:6076 (LISTEN)
java 939 payara 651u IPv6 23007 0t0 TCP 127.0.0.1:6086 (LISTEN)

MateStrysewske commented 4 years ago

I personally think that this should absolutely be the case because the Payara server should always be hidden behind an Apache whenever it's visible from the web. @MartinWahnschaffeSymeda I think you can give a few more details here.

RafaelKluender commented 4 years ago

I will put more details here, once I have really reached my goal. I now can use a demo server but no matter which login i Pick up, a banner with "an error occured" shows up. Once I have understood everything, I will pots more details here, sure.

VitaliHZI commented 3 years ago

Is there some update here, or can this issue be closed?