-
Notifications
You must be signed in to change notification settings - Fork 58
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
Installation on Ubuntu 14.04 #88
Comments
What files exist in the directory /etc/apache2/sites-enabled/? |
critic-main.conf is there from the installation |
And what's the result of loading http://the-system/? |
It was redirected to a login page and that page did not load. |
(Assuming here that you configured Critic to handle authentication, but not allow anonymous users. It sounds like it.) Oh, but then at least Critic is called correctly from Apache, or it wouldn't have been able to emit such a redirect. So Apache configuration seems reasonably working. Does "did not load" mean "produced some sort of error" or "never finished loading"? If the latter, can you use your browser's development tools to investigate what's going on, i.e. if any particular request is getting stuck or something? Or try loading the login page using a command-line tool like wget or curl, and see if that's more enlightening? |
Well let's see, the redirect to the https://host/login?target=/ finishes but at that target I get connection refused. So the redirect works from http to https within apache is correct but I don't seem to get anything loaded from critic at the login page. |
I can see apache start the wsgi and there are no errors in the critic logs or in the apache. Critic logs No activity in the apache logs when I try to access so I am a bit stumped where it is failing as the only thing I see in the dev tools is connection refused in the browser. Have you installed critic on Ubuntu 14.04 before and did it just work right away with no fiddling? |
One thing that could produce those symptoms is if you told Critic to run in mixed HTTP/HTTPS mode during installation, but haven't actually configured Apache to support HTTPS, which Critic's installation script doesn't do for you. By default, Apache wouldn't listen to HTTPS (port 443) at all, which would give you a connection refused error. If this is your problem, then you need to either make the necessary Apache configuration, or tell Critic that you're only using HTTP by setting the ACCESS_SCHEME variable in /etc/critic/main/configuration/base.py to "http". (I don't recommend using authentication over HTTP unless you know what you're doing, of course.) Ubuntu 14.04 is one of the OS versions that we run automatic testing on, so it shouldn't be a problem. |
Yeah see it now, thanks that's what I needed. Just didn't realize it when I didn't see any failures when accessing. |
Hi,
I don't seem to get the system running after installing on Ubuntu 14.04. The quickstart will launch but Apache is not running the Critic system up. I am using the newest version updated with all the default newest packages.
Anyone here able to send me a clue how to troubleshoot this, I can't seem to see anything in the logs that is helpful either in Apache or the Critic logs.
The text was updated successfully, but these errors were encountered: