Skip to content
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

Closed
garyx opened this issue Jun 1, 2015 · 9 comments
Closed

Installation on Ubuntu 14.04 #88

garyx opened this issue Jun 1, 2015 · 9 comments

Comments

@garyx
Copy link

garyx commented Jun 1, 2015

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.

@jensl
Copy link
Owner

jensl commented Jun 1, 2015

What files exist in the directory /etc/apache2/sites-enabled/?

@garyx
Copy link
Author

garyx commented Jun 1, 2015

critic-main.conf is there from the installation

@jensl
Copy link
Owner

jensl commented Jun 1, 2015

And what's the result of loading http://the-system/?

@garyx
Copy link
Author

garyx commented Jun 1, 2015

It was redirected to a login page and that page did not load.

@jensl
Copy link
Owner

jensl commented Jun 1, 2015

(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?

@garyx
Copy link
Author

garyx commented Jun 3, 2015

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.

@garyx
Copy link
Author

garyx commented Jun 3, 2015

I can see apache start the wsgi and there are no errors in the critic logs or in the apache.

Critic logs
x.x.x.x - - [03/Jun/2015:17:50:22 +0000] "GET / HTTP/1.1" 307 271 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.105 Safari/537.36 Vivaldi/1.0.190.2"
x.x.x.x - - [03/Jun/2015:17:50:23 +0000] "GET /login?target=/ HTTP/1.1" 307 293 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.105 Safari/537.36 Vivaldi/1.0.190.2"

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?

@jensl
Copy link
Owner

jensl commented Jun 3, 2015

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.

@garyx
Copy link
Author

garyx commented Jun 3, 2015

Yeah see it now, thanks that's what I needed. Just didn't realize it when I didn't see any failures when accessing.

@garyx garyx closed this as completed Jun 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants