Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The connection attempt failed #360

Open
Nialito opened this issue Jan 16, 2020 · 1 comment
Open

The connection attempt failed #360

Nialito opened this issue Jan 16, 2020 · 1 comment

Comments

@Nialito
Copy link

Nialito commented Jan 16, 2020

Hello.

I faced the following problem: after executing the sudo make up command, there were no errors, but I still can't go to the admin panel, since when accessing addresses http://localhost:9090/admin/, http://127.0.0.1:9090/admin/, http://185.148.39.153:9090/admin/ (this is the static IP address of the virtual server) the error "connection Attempt failed" is displayed.

root@graccao90:~/omaha-server# sudo make up
docker-compose -f docker-compose.dev.yml -p dev build web
Building web
Step 1/7 : FROM crystalnix/omaha-server-base:alpine
 ---> e4988a4d885b
Step 2/7 : RUN pipenv install --system --dev
 ---> Using cache
 ---> 7bc29f423fdd
Step 3/7 : ADD . $omaha
 ---> 1f3af77a2da5
Step 4/7 : RUN   mkdir /etc/nginx/sites-enabled/ &&   rm /etc/filebeat/filebeat.yml &&   rm /etc/nginx/conf.d/default.conf &&   rm /etc/nginx/nginx.conf &&   rm /etc/supervisord.conf &&   ln -s /srv/omaha/conf/nginx.conf /etc/nginx/ &&   ln -s /srv/omaha/conf/nginx-app.conf /etc/nginx/sites-enabled/ &&   ln -s /srv/omaha/conf/inflate_request.lua /var/lib/nginx &&   ln -s /srv/omaha/conf/supervisord.conf /etc/ &&   ln -s /srv/omaha/conf/filebeat.yml /etc/filebeat/ &&   chmod go-w /etc/filebeat/filebeat.yml
 ---> Running in 6b111acd9f75
Removing intermediate container 6b111acd9f75
 ---> d6865fc74642
Step 5/7 : EXPOSE 80
 ---> Running in bf0d53b3c0a4
Removing intermediate container bf0d53b3c0a4
 ---> b46a4b5ac9b9
Step 6/7 : EXPOSE 8080
 ---> Running in b4606e68bbb7
Removing intermediate container b4606e68bbb7
 ---> c4fbb766605b
Step 7/7 : CMD ["paver", "docker_run"]
 ---> Running in 4dbd55c14de0
Removing intermediate container 4dbd55c14de0
 ---> 1ccf65e0653b
Successfully built 1ccf65e0653b
Successfully tagged dev_web:latest
pipenv run paver up_local_dev_server
---> pavement.up_local_dev_server
docker-compose -f docker-compose.dev.yml -p dev up -d db
Starting dev_db_1 ... done
docker-compose -f docker-compose.dev.yml -p dev up -d web
dev_db_1 is up-to-date
Starting dev_redis_1 ... done
Recreating dev_web_1 ... done
Open http://{DOCKER_HOST}:9090/admin/
 username: admin
 password: admin

I also tried to enter the command /sbin/ip route|awk '/default/ { print $3 }':

root@graccao90:~/omaha-server# /sbin/ip route|awk '/default/ { print $3 }'
185.148.39.1

But when trying to go to this address, the error "connection Attempt failed" was also displayed.

I just noticed an interesting feature. After entering the sudo make up command, when accessing the address http://localhost:9090/admin/ or http://127.0.0.1:9090/admin/ for the first 10 seconds, the error "Connection was reset" is displayed, and then "connection Attempt failed". I don't know what this might be related to.

Please tell me what my mistake is. How do I access the admin panel?

P.S - all actions take place on Ubuntu 18.04.3 LTS (GNU / Linux 4.15.0-74-generic x86_64). I connected to localhost and 127.0.0.1 using the Mozilla browser on a virtual server.

@Nialito
Copy link
Author

Nialito commented Jan 16, 2020

@asesh, as far as I understand, you were able to run omaha-server. Can you tell me what I'm wrong about?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant