Cannot login from outside server

  • 788 Views
  • Last Post 19 August 2019
  • Topic Is Solved
AfroGarach posted this 07 August 2019

I'm on Centos 7. Port forwarding is done, firewall done. If I try telnet x.x.x.x:8080 can connect. If I try from a web browser (firefox-chrome-safari), outside network or from lan, only spins and cannot connect. From inside the server, I can login without problems. I have tried everything: SELinux off, firewall off, reinistall AMP, etc.

Order By: Standard | Newest | Votes
Mike posted this 07 August 2019

Do you have anything other than AMP on the system? If not I'd strongly recommend switching to either Debian or Ubuntu. There's something weird going on with CentOS that I cannot reproduce. It's some weirdness with the firewall.

AfroGarach posted this 07 August 2019

Hello! Nothing else running on the system, is a dedicated server. Before the last updates, AMP was running fine on CentOS 7.

Mike posted this 08 August 2019

Updates to what, CentOS or AMP?

AfroGarach posted this 08 August 2019

AMP

Mike posted this 12 August 2019

Try running the following command as root:

yum -y reinstall "*"; sync; reboot

Do not skip the reboot, I also advise taking a backup of the server before running this command.

AfroGarach posted this 13 August 2019

It didn’t work.

Mike posted this 14 August 2019

Hmm, does a new instance have the same issue?

AfroGarach posted this 14 August 2019

Yes

Cytecor posted this 14 August 2019

I'm having the same issue. I've uninstalled firewalld (it was disabled before and still had the same problem) and the problem is still occurring.

I tested with a brand new installation of centos 7.6 and a new install of amp 1.8.3.4 and it occurs there too.

A netstat -l shows that 8080 is not listening.(with or without the firewall installed)

Justin posted this 15 August 2019

I am having the same issues. Not able to figure out a fix for this. No attempt at troubleshooting seems to be working

Mike posted this 15 August 2019

What does AMPs log say? Also check ampinstmgr ports INSTANCENAME to see what it shows as listening/open.

Justin posted this 15 August 2019

What does AMPs log say? Also check ampinstmgr ports INSTANCENAME to see what it shows as listening/open.

[Info] Instance is currently running.

[Info] LISTENING 8086 TCP (Core.Webserver.Port)

[Info] LISTENING 25565 TCP (MinecraftModule.Minecraft.PortNumber) - Unverified

Ports are open through system firewall and network

Mike posted this 15 August 2019

Firewalld is a frontend on iptables, does iptables show rules that would allow the ports thru?

AfroGarach posted this 15 August 2019

Output

ampinstmgr ports ADS01
[Info] AMP Instance Manager v1.8.3.2 built 31/07/2019 14:42
[Info] Release spec: Release - built by CUBECODERS/BuildBot on CCL-DEV
[Info] Port usage for ADS01 (ADS01)
[Info] Instance is currently running.
[Info] LISTENING    8080    TCP (Core.Webserver.Port)

AfroGarach posted this 15 August 2019

Yes: ACCEPT tcp -- anywhere anywhere tcp dpt:webcache ctstate NEW

Mike posted this 15 August 2019

Try running the following (as root)

iptables -A INPUT -m state --state NEW -p tcp --dport 8080 -j ACCEPT

Replacing 8080 with whatever port ADS is running on.

AfroGarach posted this 15 August 2019

No, that didn’t work.

Mike posted this 16 August 2019

If you set up a reverse tunnel in SSH can you connect that way?

AfroGarach posted this 16 August 2019

No, but with SSH tunel, at least opens the website, but without the login fields, only shows the AMP logo...

Mike posted this 17 August 2019

Ah, press CTRL+F5 when you're in that state.

AfroGarach posted this 17 August 2019

Really? Of course I have refreshed the screen several times...

Mike posted this 17 August 2019

Hmm, there's something going on specifically with CentOS, but I can't reproduce it at all. It's not something everyone seems to suffer from. If you're able to connect at all via a tunnel though it does point to a firewall issue. If you're not using the system for anything other than AMP I'd suggest switching to Debian/Ubuntu Server if you're able to.

Justin posted this 18 August 2019

Hmm, there's something going on specifically with CentOS, but I can't reproduce it at all. It's not something everyone seems to suffer from. If you're able to connect at all via a tunnel though it does point to a firewall issue. If you're not using the system for anything other than AMP I'd suggest switching to Debian/Ubuntu Server if you're able to.

Is there any other remedy we can attempt other than going to a new distro? I'm willing to help with the troubleshooting of this issue.

Mike posted this 18 August 2019

I can't even reproduce the issue. A fresh CentOS setup doesn't seem to exhibit this. If you are able to reproduce the issue from a fresh setup then I'd have somewhere to start.

Mike posted this 19 August 2019

I've just managed to reproduce the issue on a local CentOS installation. I'm now looking into the matter.

Mike posted this 19 August 2019

Okay so I was able to fix it thusly:

Run all of the following as root:

yum update
wget dl.fedoraproject.org/pub/epel/7/x86_64/Packages/e/epel-release-7-11.noarch.rpm
rpm -ihv epel-release-7-11.noarch.rpm
yum install iptables-services htop
yum -y reinstall "*"
sync
reboot

Do not skip the reboot!

After running this, AMP was behaving as expected.

AfroGarach posted this 19 August 2019

Run all of the following as root:

yum update
wget dl.fedoraproject.org/pub/epel/7/x86_64/Packages/e/epel-release-7-11.noarch.rpm
rpm -ihv epel-release-7-11.noarch.rpm
yum install iptables-services htop
yum -y reinstall "*"
sync
reboot

That works! Now is running fine, thanks!

Close