I enabled galaxy.yml (cp’ing from galaxy.yml.sample so I could give a datascientist admin rights to this instance) and ever since I did that, nothing else the site is no longer accessible externally. I edited the http statement (changing it from the self assigned 127.0.0.1:8080 to 0.0.0.0:8080) and it would STILL run the site on 127.0.0.1, The only thing that worked was putting the 0.0.0.0 in quotes…then the output I would see when running the run.sh script would show what I was trying to edit. That still didnt work so I decided to make the IP address what the ACTUAL ip address is (not ideal since I either have to pick the internally facing IP or the external IP) but the site is still not accessible outside of the localhost. The port is open on our AWS security group. UFW is not running (This is a Ubuntu 16.04 machine).
Again this host was working exactly as it was supposed (minus the instructions either being wrong or missing on the site but thats a whole other issue) until I copied to the galaxy.yml file. I cant even revert. I tried deleting the file in the hopes I could reverse this issue and its STILL exhibiting the same problem. This is seems like a stupid problem but I have burned all day on it and gotten no where