Arches 5.1 AWS Ubuntu Connection refuse

[Tom Corrigan]

Have installed Arches 5.1 on an AWS Ubuntu instance. Connection to localhost:8000 refused after running the Django server. Elasticsearch is running on port 9200. Please advise as to other areas to investigate.

[Ryan]

Hi Tom,

The first thing I would check is that port 8000 is open to the world in the security group attached to that instance. I think port 80 is open by default on EC2 instances but not necessarily 8000.

If the port is open and this doesn’t work you could also trying running the dev server while indicating the ip and port. So it would look like this :

python manage.py runserver 0.0.0.0:8000

The top post here describes why running the dev server on a remote machine without the 0.0.0.0 might not work.

https://stackoverflow.com/questions/5768797/manage-py-runserver#5768853

In addition, you can change the port in the runserver command to 80 if you’d like.

Hope this helps. Let us know how it goes.

Cheers,

Ryan

On May 13, 2021, at 7:36 PM, Tom Corrigan <tcc...@gmail.com> wrote:

Have installed Arches 5.1 on an AWS Ubuntu instance. Connection to localhost:8000 refused after running the Django server. Elasticsearch is running on port 9200. Please advise as to other areas to investigate.

--
-- To post, send email to arches...@googlegroups.com. To unsubscribe, send email to archesprojec...@googlegroups.com. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en
---
You received this message because you are subscribed to the Google Groups "Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to archesprojec...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/archesproject/38c02a1c-4f82-4b4b-8ca7-c27df980b310n%40googlegroups.com.

[Tom Corrigan]

This problem solved. Running on an AWS virtual server using an Elastic IP address for external access. That external address has to be in Django's ALLOWED_HOSTS list i n settings.py. And the server has to be run referencing the actual internal IP address of the virtual server, e.g., python manage.py runserver 172.31.36.91:8000.

While these changes allow me to access the portions of the web site that don't require you to be logged in I now get a Connection Refused when I attempt to submit my credentials for creating a new account. Failure occurs on line 796 of create_connection.