Simply Staking Community

21 Nov 2022 13:32

Maybe that’s why I did not work earlier because I was using firewall and allowed 8000 instead of 9000

Simply Staking Community

21 Nov 2022 12:23

Prometheus and node exporter works fine just having issues with the tendermint RPC

Simply Staking Community

21 Nov 2022 12:09

i got panic installed on a fresh server and it worked

Simply Staking Community

21 Nov 2022 10:47

this should be run in panic dir right?

Simply Staking Community

21 Nov 2022 10:44

we can try a restart... let's see

Simply Staking Community

21 Nov 2022 10:32

docker logs 0db717547042

Simply Staking Community

21 Nov 2022 10:28

run docker-compose logs panic_api_1

Simply Staking Community

21 Nov 2022 10:27

is that supposed to be so?

Simply Staking Community

21 Nov 2022 10:27

one more thing my docker-compose version shows build unknown

Simply Staking Community

21 Nov 2022 10:10

https://panic_ip:9000 right? Because am accessing it externally not locally

Simply Staking Community

21 Nov 2022 10:09

Yeah accepted the unsafe certificate but that’s for the UI access but for the https://localhost:9000, it did not prompt any cert warnings

Simply Staking Community

21 Nov 2022 10:07

Also I do not understand how you get a blank page on https://localhost:9000. At most you either get the api docs, or you get a warning saying it might be unsafe.

Simply Staking Community

21 Nov 2022 09:59

i realy the first time installation of panic with the previous version and was able to access the panic ui

Simply Staking Community

21 Nov 2022 09:56

yes just checked now its pointed to my ip and not x.x.x.x

Simply Staking Community

21 Nov 2022 09:54

Go on line 11 in panic/.env. Are you sure the UI_ACCESS_IP is not set to X.X.X.X ?

Simply Staking Community

21 Nov 2022 12:59

9000 not 8000 : the old panic had the installer on 8k, this one does not

Simply Staking Community

21 Nov 2022 12:22

For the first installation I can’t get the tendermint RPC work

Simply Staking Community

21 Nov 2022 11:25

is there any port i need to open on panic server again other than this?

Simply Staking Community

21 Nov 2022 10:45

sudo docker-compose kill
sudo docker system prune -a --volumes
sudo docker-compose up -d --build

Simply Staking Community

21 Nov 2022 10:35

So weird. Everything is running as intended

Simply Staking Community

21 Nov 2022 10:30

docker ps

Simply Staking Community

21 Nov 2022 10:28

for sure not an issue with docker since all build and panic is indeed running

Simply Staking Community

21 Nov 2022 10:27

docker-compose version 1.25.0, build unknown

Simply Staking Community

21 Nov 2022 10:23

have tried this as well same thing

Simply Staking Community

21 Nov 2022 10:10

Out of curiousity, try http instead of https, so http://localhost:9000

Simply Staking Community

21 Nov 2022 10:07

Usually after you bypass with thisisunsafe (for chrome i believe), all works well. Try access via Chrome if you haven't done so already.

Simply Staking Community

21 Nov 2022 10:06

Make sure you accept the certificates on both the API and the UI

Simply Staking Community

21 Nov 2022 09:56

and you're saying that if you access https://localhost:9000 is inaccessible completely?

Simply Staking Community

21 Nov 2022 09:55

the panic UI is assessable but page is blank then after sometime the above error pops up on the page

Simply Staking Community

21 Nov 2022 09:52

Everything seems to be running well in docker... hmm...