Note - If you do not fill in every section below, your post won’t be answered - you must provide the steps you have followed so far and the actions you’ve already taken. Make sure to remove this notice from your post too.
Make sure you search before posting! Duplicate posts for the same issue may not be answered.
OS Name/Version: Debian GNU/Linux 12 (bookworm)
Product Name/Version: AMP 2.6.0.0
Problem Description: I tried to use the getamp postSetupHTTPS command but it ended up failing at the certbot stage. I no longer want to use HTTPS but now when I go to SERVER_IP:8080 on a machine on the same network I get nothing rather than the AMP control panel that I’m used to seeing.
Steps to reproduce:
Step 1 run getamp postSetupHTTPS
Step 2 Follow prompts until it fails
Actions taken to resolve so far: Run apt-get purge nginx nginx-common and ampinstmgr reconfigure ADS01 +Core.Webserver.UsingReverseProxy False
You could try running ampinstmgr updatefirewall as root to see if AMP will re-add it for you now that you’ve changed the reverse proxy configuration.
Otherwise you’ll have to use your Debian install’s firewall command (can’t remember it off the top of my head, I haven’t worked with IPTables all that much)
Still no luck. However it says You should now run 'ampinstmgr repairauth' on this system as well as any other AMP targets. after the rebind but when I run that command it asks me Which mode is ADS configured as? 'standalone', 'controller', 'target' or 'hybrid'? If you do not know, press CTRL+C to abort and I do not know haha
Okay, so I enter standalone and it then asks me What is the URL of your controller/standalone instance? This URL must be accessible from all targets in a multi-target setup.