Installation on Ubuntu 14.04 about critic HOT 9 CLOSED

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

from critic.

critic-main.conf is there from the installation

from critic.

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

from critic.

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

from critic.

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

from critic.

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.

from critic.

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?

from critic.

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.

from critic.

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

from critic.