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

Connection refused with docker installation #240

Open
juanluisbaptiste opened this issue Feb 5, 2021 · 2 comments
Open

Connection refused with docker installation #240

juanluisbaptiste opened this issue Feb 5, 2021 · 2 comments
Labels

Comments

@juanluisbaptiste
Copy link

juanluisbaptiste commented Feb 5, 2021

Reproduction

Steps to reproduce:

  1. Follow docker install instructions at https://getfal.co/docs/getting-started/installation
  2. Use the example docker-compose.prod.yml file
  3. Configure the .env.prod file, add for example ALLOWED_HOST=falco
  4. Add falco hostname to your hosts file pointing to your laptop or server, ie:
sudo echo "192.168.0.10 falco" >> /etc/hosts
  1. Open in a browser http://falco
  2. Falco returns a redirection to https://falco which ends in a connection refused error.

Expected Behavior

Falco login page should be loaded

Actual Behavior

A connection refused error:

curl -IL http://falco
HTTP/1.1 301 Moved Permanently
Server: 
Date: Fri, 05 Feb 2021 04:37:21 GMT
Connection: close
Content-Type: text/html; charset=utf-8
Location: https://falco/
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block

curl: (7) Failed to connect to falco port 443: Connection refused

Environment

Using example docker-compose.prod.yml and .env.prod.dist example files (only changing postgres db password env variables as noted in issue #239 ).

  • Browser(s): Firefox 85.0
  • Operating System (e.g. Windows, macOS, Ubuntu): Kubuntu 20.04
@fargito fargito added the docker label Apr 16, 2021
@MParvin
Copy link
Contributor

MParvin commented Apr 14, 2022

Dear @juanluisbaptiste
did you use a reverse proxy with SSL?

As written in the documentation:

For production use, we recommend using a PostgreSQL with valid SSL certificates and expose the application with a frontal server managing the HTTPS certificates. Without a valid SSL certificate, the application will not work.

@juanluisbaptiste
Copy link
Author

@MParvin no I didn't I followed the documentation to test it out, why think in a production setup if I was not able to even get it running in my laptop.

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

No branches or pull requests

3 participants