I enabled HTTPS on my AMP instance and locked myself out

[Sara_Riso]

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 12

Product Name/Version: AMP 26.0.0.0 Phobos

Problem Description: I used the enable HTTPS feature from the command line and now I cannot access the GUI anymore after a certificate error. How can I revert AMP back to using port 8080?

If you're sharing console output, logs, or commands you have run, please make sure to use code tags 
(3x backticks for blocks, 1x backtick for a single line) to help make posts readable. This also
provides syntax highlighting.

Steps to reproduce:

• Step 1
• Step 2
• Step 3

Actions taken to resolve so far: Resetted the instance

[Abnormal]

Have you tried to go to https://ipaddress?

[Sara_Riso]

Gives me This site can’t be reached

10.0.1.50 refused to connect.

Try:

• Checking the connection
• Checking the proxy and the firewall

ERR_CONNECTION_REFUSED

[Abnormal]

Did you follow this guide when setting up?

Setting up secure HTTP (HTTPS) with AMP

[Documentation (2)] There are a number of methods that can be used to set up secure HTTP (HTTPS) within AMP depending on your use case. Note that with AMP Enterprise, use of HTTPS is mandatory. 1. Reverse proxy via nginx (recommended, Linux only) If you use the default getamp.sh setup script to install AMP, and you select the option to set up HTTPS when running that script, AMP installs and configures an nginx reverse proxy and Let’s Encrypt certificate handled by certbot to provide secure …

Can you log into the vm and check the logs for ads01?

[Sara_Riso]

I’m sorry but how do I do that again? I know how to access the amp user.

[Abnormal]

To enable the logs use
ampinstmgr reconfigure ADS01 +Core.Monitoring.LogLevel 0

Diagnosing AMP/Application startup issues

[image] Most issues with AMP are usually caused by minor configuration issues that can be easily solved. Diagnosing application startup issues AMP can produce startup scripts equivalent to what it’s trying to start to let you start applications from outside of AMP to view any extra console output and to reproduce behaviour outside of AMP. Stop the instance, and then in AMPConfig.conf for your instance turn on both Monitoring.ProduceStartupScripts and Security.LogSensitiveProcArgs. With thes…

Read through this for viewing the log. When I get home later I can assist more.

[Abnormal]

Hi Sara, not sure if you got any further on your issue today.

but if you’d like to check your logs you can do so by getting into the docker instance with the following commands.

log into VM
get into the AMP user.

su -l amp

ampinstmgr --lastlog instancename

scratch this below:
docker exec -it DockerInstance bash
cd /AMP/AMP_Logs/
and see the latest log in that direction. if you’re using the cli you can use cat logfilename.log

[ThePotatoKing]

Why do you keep suggesting that people exec into the Docker container? The files are readily available.
You can even run ampinstmgr lastlog TheInstanceName to see them

[Abnormal]

I did correct this. I’m used to just exec into the docker instance. my apologies PotatoKing.