-
-
Notifications
You must be signed in to change notification settings - Fork 263
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
Error 500 #52
Comments
Okay. So I fiddled with it a bit more. It seems that when I change the configuration to this:
The things like /login and stuff work great. However going to simply example.com/ and gives me a 403. However reverting back to the previous one fixes it and reverses it. Going to example.com/index does work however. Gah. |
Did you use the example Nginx config? I try using it and work fine, CentOS+Nginx.
|
I will try it again, but it did not appear to work last time. Also, I am running on Ubuntu Server. |
Nope. Still a 403 when I go to example.com and a success when I go to example.com/index. Any other ideas? EDIT: Wait. Actually, it's a 502 for example.com/index. Interesting. |
it's run on localhost ? |
Um. Yeah, I think so. I mean, I have a domain pointing to it, but yes. It is running on localhost I am pretty sure. How would I check? EDIT: If you mean on my personal machine, no. I am running on a VPS. |
i mean, make sure webserver (nginx) work in your localhost, & try htmly run well on locahost before pointing to domain, |
I would, but the testing environment wouldn't be the same. I am running Mac OS X and don't really have an option to install refit or whatever it is called. |
try clear browser cache, or restart nginx 💨 , sorry if it does not help |
Sadly, I have tried both of those. If anyone else wants to chime on on successes with HTMLy and nginx, by all means. |
Ahah! Okay. I have figured it out and you should definitely add this to the README. Here is the config that worked:
And that works with everything. The other thing is that you have to make sure that php5-fpm was set up properly. My issue was that it was running on the sock, while I was telling it to listen on 127.0.0.1:9000. The two need to be the same in both files, and for me, the IP based one didn't work at all. So yeah. Wooo! It works! |
Congratulation ! @HowardStark :) |
Hello!
I have been struggling for close to 6 hours now on trying to get this to run. I really really want this, but for whatever reason, I just can't. The site itself works fine, but when I try to go to any actual pages, such as example.com/login, it throws an error 500. I have looked up a bunch of solutions but nothing seems to run. I am using nginx and using my own configuration since yours just doesn't work. I am running nginx on Ubuntu 13.10 Server.
/etc/nginx/sites-available/default:
At the moment, I am just trying to get the bare minimum to work. Then I will add the config block etc.
I have no idea anymore.
The text was updated successfully, but these errors were encountered: