I am having trouble trying to get passenger to work, even on a newly-created application using the 'rails' command. What I am doing is:
Set up a domain with Passenger enabled (data.tarifadetaxi.com), and pointed it to /home/username/tarifadetaxi/public
While at /home/username, I ran the following commands:
- rails tarifadetaxi
- cd tarifadetaxi
- touch tmp/restart.txt
If I go to http://data.tarifadetaxi.com/ , I see the rails welcome page, but it is because it is a static file at ~/tarifadetaxi/public. However, if I try to fetch anything that would be directed to rails code, I get an empty page. Examples:
The server simply closes the connection and doesn't return any reply:
$ curl -v http://data.tarifadetaxi.com/rails/info/properties
* About to connect() to data.tarifadetaxi.com port 80
* Trying 22.214.171.124... connected
* Connected to data.tarifadetaxi.com (126.96.36.199) port 80
- Empty reply from server
- Connection #0 to host data.tarifadetaxi.com left intact
curl: (52) Empty reply from server
- Closing connection #0
I don't get any message on the rails log directory, neither on the ~/logs/datatarifadetaxi.com/http/*.log files, either. I see stuff on the domain logs only when an static file is requested.
Any hints on how to troubleshoot this?
I've asked DH support for help on this, but I was told it is beyond the scope of their support. I would understand that if it was a complex application, but having it broken even on a freshly-created app using the 'rails' command on DH server, I feel like uploading an index.html file on your domain directory, not getting it shown when accessing the domain, not having access to the domain log files, and being told it is not their problem.