Hi, I’ve recently installed a Snomed terminolgy server on a new fresh instalation of OpenSUSE 15.1.
The problem is I can´t access the terminology server (SnowStorm) from the local network.
Tipically it should be accesible at
http://<ip-address>:8080/
But it’s not. I can ONLY access it from
http://localhost:8080/
I’m pretty new to OpenSUSE
any help greatly appreciated
Thanks!
Well, the IP address for localhost is 127.0.0.1. You did not show what you try. Can we assume that it is different?
And then, how can we be sure that that is an IP address of the system?
BTW, I have Apache running here on a system and I can access it from Firefox on the same system by both localhost and 10.0.0.154.
Do you have any restrictions in your server configuration on who is allowed?
I have e.g. in my apache config
Require ip 10.0.0
Require host localhost
which restricts and allows to my LAN and my system.
Hi, and thanks for both answers!
First I must tell that I´m not using Apache at all
Concerning your first answer:
Yes, localhost resolves to 127.0.0.1 on this system.
Here’s the response from wget issued on the servers console
snwstrm1-s15c1:/ # wget localhost
--2020-08-03 18:11:50-- http://localhost/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:80... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:80... failed: Connection refused.
However you can see, there’s nothing listening on port 80
But when I try same command with port 8080 I get this answer from the snowstorm server
snwstrm1-s15c1:/ # wget localhost:8080
--2020-08-03 18:12:19-- http://localhost:8080/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8080... connected.
HTTP request sent, awaiting response... 302
Location: http://localhost:8080/swagger-ui.html [following]
--2020-08-03 18:12:19-- http://localhost:8080/swagger-ui.html
Reusing existing connection to [localhost]:8080.
HTTP request sent, awaiting response... 200
Length: 2927 (2.9K) [text/html]
Saving to: ‘index.html’
index.html 100%=====================================================================================>] 2.86K --.-KB/s in 0s
2020-08-03 18:12:19 (269 MB/s) - ‘index.html’ saved [2927/2927]
Also is ElasticSearch listening on port 9200
wget localhost:9200
--2020-08-03 19:04:08-- http://localhost:9200/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:9200... connected.
HTTP request sent, awaiting response... 200 OK
Length: 493 [application/json]
Saving to: ‘index.html.1’
index.html.1 100%=====================================================================================>] 493 --.-KB/s in 0s
2020-08-03 19:04:08 (52.8 MB/s) - ‘index.html.1’ saved [493/493]
I´m wondering if this could be caused by the firewall?
Don´t know how should I test it
This is an update.
I’ve stopped the firewall with
systemctl stop firewalld
and my snowstorm came alive from local network!
Which leads me to another quest
How should I open this 8080 port or perhaps service/protocol?
the communication is based on the interchange of http headers GET , POST
but I have emphasize there is no apache nor any other web server(as far as I know)
This is implemented via some .jar files executed by java (that is the snowstorm server)
Any way the key here is to instruct the firewall to let the tcp/ip communication flow thru this port
Any help greatly appreciated
YaST > Security and Users > Firewall?
I do not use firewalld (or any other), but when you use it, you should not be surprised that it blocks ports like 8080.
Well my YaST says it doesn’t have a module to configure/control the firewall
Error
YaST currently does not have a module for configuring firewall. Please,
either use "firewall-config" to configure your firewall via a user interface
or "firewall-cmd" for the command line.
[OK]
And my SuSE is installed with text mode only so I guess I should be learning how to use such firewall-cmd
I do not use firewalld (or any other), but when you use it, you should not be surprised that it blocks ports like 8080.
Yeah, me neither. Just thought it could be a good idea to accept the installer default options 
So. Thanks for your help.
I don´t know if I should reformulate my question/topic as this has clearly changed into “How to use firewall-cmd to open port 8080”
Should I ?
Yet another update.
Used this comand :
firewall-cmd --zone=public --permanent --add-port=8080/tcp
Verified with
snwstrm1-s15c1:~ # firewall-cmd --zone=public --permanent --list-ports
9200/tcp 9300/tcp 8080/tcp
But still can’t connect
I guess theres something more I need todo to allow this communications, but what?
Ok. Finally It’s working!!
Needed to restart the firewall so it would implement the changes made when adding pot 8080
So the solution to my problem was:
firewall-cmd --zone=public --permanent --add-port=8080/tcp
systemctl restart firewalld
I’m very happy with this finding lol!
And want to thank to hcvv[size=2] for the suppport and helping me to analize the problem
Thanks
Mauricio
[/size]
You are welcome.
It is fine that you only needed some vague suggestions from me to solve it yourself. Must be satisfying.