WebUI not running, happens few days after reboot

Never touch a running system :wink:

When I restart my Linux machine, everything seems fine for a few days, but then, I cannot access my WebUI anymore, servers seem to keep running. I get connection refused error in browser.

If I hit : sudo su -l amp -c “ampinstmgr status” I get:

[Info/1] AMP Instance Manager v2.5.1.8 built 17/09/2024 12:32
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Instance Name │ Friendly Name │ Module │ IP │ Port │ U p
───────────────────┼──────────────────┼────────────┼─────────────────┼───────┼── ─
ADS01 │ ADS │ ADS │ 0.0.0.0 │ 8080 │
ConanExilesServ… │ Conan Exiles … │ Generic │ 127.0.0.1 │ 8082 │ ✓
Factorio2001 │ Factorio 2.0 │ Generic │ 127.0.0.1 │ 8084 │ ✓
PalworldServerC… │ Palworld Serv… │ Generic │ 127.0.0.1 │ 8081 │ ✓
S7DaysServerChr… │ 7 Days Server… │ Generic │ 127.0.0.1 │ 8083 │ ✓

What I then do is to restart the whole machine, which works fine for a few days…
What can I do? Worked fine for the last few month, but then I had to update Ubuntu 22.04.5 and AMP and here we are.

Please give advice for further information, I´m a Linux noob

Thanks for your help

You don’t have to restart the machine, just run ampinstmgr start ADS01

ok, thx for the hint. Tried it, kinda weird things happen:

Instance Name │ Friendly Name │ Module │ IP │ Port │ Up
───────────────────┼──────────────────┼────────────┼─────────────────┼───────┼───
ADS01 │ ADS │ ADS │ 0.0.0.0 │ 8080 │
ConanExilesServ… │ Conan Exiles … │ Generic │ 127.0.0.1 │ 8082 │ ✓
Factorio2001 │ Factorio 2.0 │ Generic │ 127.0.0.1 │ 8084 │ ✓
PalworldServerC… │ Palworld Serv… │ Generic │ 127.0.0.1 │ 8081 │ ✓
S7DaysServerChr… │ 7 Days Server… │ Generic │ 127.0.0.1 │ 8083 │ ✓

chris@linuxgameserver:~$ ampinstmgr start ADS01
[Info/1] AMP Instance Manager v2.6 built 25/10/2024 12:24
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Error/1] No such instance matching name: ‘ADS01

I can see my instance is called ADS01, but if I want to start it it says No such instance ?!?

But even if it worked, I would prefer not to do so every few days :wink: So let´s take a look into the problem pls

I’d suggest taking a look through the logs to find out what happened.
You can run ampinstmgr lastlog ADS01, or see if using the friendly name works if that throws an error.
Worst case you can browse to /home/amp/.ampdata/instances/ADS01/AMP_Logs as the amp Linux user

Ah, just realized you’re running commands as your own user, that won’t work.
Run sudo su -l amp to log into the amp user (there’s usually a large yellow message when you don’t use the amp user)

had this issue when I updated my instances, make sure to

  • Run as root or sudo
  1. apt-get update && apt-get upgrade
  • Run as amp user as specified by ThePotatoKing
  1. ampinstmgr --upgradeall

oh, my mistake…sry for that…I switched to amp user and then I could restart my ADS01 instance…works fine…trying to check the logs tonight to see…thx for your help. Im still confused with the different users and the sudo command.
I updated to 2.6 sucessfully, maybe that helps? we´ll see. works fine for 2 days now. maybe it´s just the update that needed to be done :wink: