Unable to enable certain modules

[shrey]

When trying to enable the ssl module, using: a2enmod ssl, i'm running into this:

root@451e4844-.......6e3e69d:/app/code# a2enmod ssl

Considering dependency setenvif for ssl:
Module setenvif already enabled
Considering dependency mime for ssl:
Module mime already enabled
Considering dependency socache_shmcb for ssl:
Enabling module socache_shmcb.
Could not create /etc/apache2/mods-enabled/socache_shmcb.load: Read-only file system

even though, the socache_shmcb module does seem to be available, as i can see it in /etc/apache2/mods-available/

---

How to resolve this situation, as i need to enable proxying of bot requests to a prerendering service, in the .htaccess file?

RewriteRule ^(.*)$ https://service.prerender.io/%{REQUEST_SCHEME}://%{HTTP_HOST}/$1 [P,L]

[girish]

@shrey we can enable it in the app package.

[girish]

Re-reading the question... P is the proxy flag which requires mod_proxy. This is already enabled. mod_ssl is something else - https://httpd.apache.org/docs/current/mod/mod_ssl.html . Can you check or tell us why you need this?

[shrey]

@girish said in Unable to enable certain modules:

mod_ssl is something else - https://httpd.apache.org/docs/current/mod/mod_ssl.html . Can you check or tell us why you need this?

Hi @girish

I need the mod_ssl because i found that the above mentioned RewriteRule to an https url doesn't work, unless mod_ssl is enabled.

[shrey]

This post is deleted!

[shrey]

@girish
LAMP error log:

No protocol handler was valid for the URL /about (scheme 'https'). If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.

[joseph]

@shrey said in Unable to enable certain modules:

RewriteRule ^(.*)$ https://service.prerender.io/%{REQUEST_SCHEME}://%{HTTP_HOST}/$1 [P,L]

Is this even correct? there are two ":" . not an expert but something seems off here

[shrey]

@joseph
Checked again. The second ":" is used correctly.

But, regardless of that, the exact URL that i'm currently using in the live RewriteRule is unambiguous (syntax: https://example.com/path1?param1=$1)

[shrey]

@girish @joseph

Is there a quick workaround for this, in case a permanent solution is not possible immediately?

[girish]

@shrey I can publish a new package now with ssl mod enabled. Just building it now.

[girish]

@shrey I pushed an update that enables it now

[shrey]

@girish Thanks for the quick resolution!