Posts by BratHuhn

Many Thanks!

Just wanted to try it out but got some errors during installation - you may can help me?

Problem 1

- The requested package roundcube/plugin-installer (locked at 0.1.8, required as ~0.2.0) is satisfiable by roundcube/plugin-installer[0.1.8] but these conflict with your requirements or minimum-stability.

Problem 2

- The requested package phpunit/phpunit (locked at 9.5.4, required as ^4.8.36 ^5.7.21) is satisfiable by phpunit/phpunit[9.5.4] but these conflict with your requirements or minimum-stability.

Problem 3

- The requested package kolab/net_ldap3 (locked at dev-master) is satisfiable by kolab/net_ldap3[dev-master] but these conflict with your requirements or minimum-stability.

Problem 4

- The requested package pear-pear.php.net/net_ldap2 could not be found in any version, there may be a typo in the package name.

Problem 5

- phpunit/phpunit 4.8.36 requires phpunit/php-code-coverage ~2.1 -> satisfiable by phpunit/php-code-coverage[2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.1.7, 2.1.8, 2.1.9, 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.4].

EDIT - Fix:

- Removed lock file

- Started composer installation manually

- Got some other errors which could be fixed by removing the vendor/pear folder

You can reset The Error Message in system Tools / debugging

Works perfectly!

Quote from aaroniker

Just a quick update for the view if you are logged in as another account

loggedin.png

Great Work!!! Quite Happy that you are still have time and Enthusiasm for this hard Work.

Gesendet von meinem LG-H815 mit Tapatalk

Quote from Nuxwin

@BratHuhn

I was wrong with my previous sentences. You can try something like:

Code

1. RewriteEngine On
2. RewriteCond %{HTTPS} !=on
3. RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L]

in the /etc/apache2/imscp/<domain.conf> and then reload your apache configuration.

BTW: You can use the same statement in .htaccess (even if you use fastcgi).

Source: https://wiki.apache.org/httpd/RewriteHTTPToHTTPS

Display More

Those lines did the trick - now it works.
Btw I was an idiot, those lines were additionally on the false position in the conf-files -.-

Thanks guys!

Hi,

when I am right I couldn´t use an .htaccess because seafile is using fastcgi. So the forwarding should be done by apache configuration.
Is there another way to influence the forwarding?

Where would be the right place for this configuration as it is actually not possible to use seperate files for port 80 and 443?

Thanks for hint but I am already using this codeblock in the vhost conf.

• RewriteCond %{HTTPS} off
• RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R]

it seems not to work after restarting apache.
Calling http://xxx.tld is not being redirected to https://xxx.tld

Hello,

just tried those lines in the imscp/domain.tld.conf
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

But the domain is not always forwarded to https
Apache has been restarted

Maybe a suggestion?

Okay found the solution.

Since seafile managed to edit some settings in the seahub webinterface I had to edit them there and not in the conf-files.

Adding the missing https @FILE_SERVER_ROOT in the webinterface settings brings the fix!

Hi,

right this is what I understanded. The module is activated and the corresponding line is added in apache2.conf.
I will contact seafile support team.

Just a quick question. Which version of apache are you using as it is working for you?