Hi
On a Debian stable server, I installed Coquelicot and followed /usr/share/doc/coquelicot/README.Debian
For some reason, this install will let me use Coquelicot via http, but not https. I don't mind too much for the upload part (perhaps I should), but I would like the download url to work via https
When trying to access the upload service via https, Firefox will warn: ssl3_get_record:wrong version number, and Chromium says: ERR_SSL_PROTOCOL_ERROR
I see nothing in the server logs that helps me.
Anybody have any ideas?
this is what I added to the /usr/share/doc/coquelicot/examples/coquelicot.apache2 sample configuration copied into sites-enabled/coquelicot
(port and link are not the real values)
<Location /link> ProxyPass http://127.0.0.1:port/link SetEnv proxy-sendchunks 1 RequestHeader set X-Forwarded-SSL "on" </Location>
Thx
G
By the way: on Debian the package is marked for autoremoval on 5 May due to ruby-minitest-shared-description: #893823
Hi,
On 18-04-03 11:07:20, Gijs Hillenius wrote:
Anybody have any ideas?
I can't comment on your actual question, but...
By the way: on Debian the package is marked for autoremoval on 5 May due to ruby-minitest-shared-description: #893823
...this is a false positive: The bug was already fixed (via an upload) some days ago, but the Debian infra is lagging behind. IOW: It won't be removed.
Cheers, Georg
Hi Gijs,
Gijs Hillenius:
On a Debian stable server, I installed Coquelicot and followed /usr/share/doc/coquelicot/README.Debian
For some reason, this install will let me use Coquelicot via http, but not https. I don't mind too much for the upload part (perhaps I should), but I would like the download url to work via https
When trying to access the upload service via https, Firefox will warn: ssl3_get_record:wrong version number, and Chromium says: ERR_SSL_PROTOCOL_ERROR
I see nothing in the server logs that helps me.
Anybody have any ideas?
Have you run `a2enmod ssl proxy_http headers`?
This sounds like the `ssl` module is not enabled.
HTH,
On 4 Apr 2018, Lunar wrote:
Hello, and thanks for the responses
Hi Gijs,
Gijs Hillenius:
On a Debian stable server, I installed Coquelicot and followed /usr/share/doc/coquelicot/README.Debian
For some reason, this install will let me use Coquelicot via http, but not https. I don't mind too much for the upload part (perhaps I should), but I would like the download url to work via https
When trying to access the upload service via https, Firefox will warn: ssl3_get_record:wrong version number, and Chromium says: ERR_SSL_PROTOCOL_ERROR
I see nothing in the server logs that helps me.
Anybody have any ideas?
Have you run `a2enmod ssl proxy_http headers`?
This sounds like the `ssl` module is not enabled.
both modules are enabled.
What I've tried - without the desired effect - is pointing to the LetsEncryt SSLCertificateFile and SSLCertificateKeyFile, that gives the same error.
Gijs Hillenius:
On 4 Apr 2018, Lunar wrote: Hello, and thanks for the responses
Hi Gijs,
Gijs Hillenius:
On a Debian stable server, I installed Coquelicot and followed /usr/share/doc/coquelicot/README.Debian
For some reason, this install will let me use Coquelicot via http, but not https. I don't mind too much for the upload part (perhaps I should), but I would like the download url to work via https
When trying to access the upload service via https, Firefox will warn: ssl3_get_record:wrong version number, and Chromium says: ERR_SSL_PROTOCOL_ERROR
I see nothing in the server logs that helps me.
Anybody have any ideas?
Have you run `a2enmod ssl proxy_http headers`?
This sounds like the `ssl` module is not enabled.
both modules are enabled.
There's three different modules on the above command line.
What I've tried - without the desired effect - is pointing to the LetsEncryt SSLCertificateFile and SSLCertificateKeyFile, that gives the same error.
Could you try to do `curl -I http://addr:port/%60 to see if SSL is enabled or not?
What value has `SSLProtocol`?
This does not seem to be an issue specific to Coquelicot, so this list might not be the best place to get help.
Hello
I fixed it: after studying the apache documentation, I figured out I was making mistakes with an existing <directory> and coquolicot's <location> tweaks.
sorry for the noise
-
Georg Faerber -
Gijs Hillenius -
Lunar