By the way - someone told me that i will crash my whole System if i try to install openssl 32 Bit manualy because openssl is a Core Part of OpenSuSe and if i manualy put the 32 Bit Version on it nothing will be like befor

I hope my bad English is not the first Problem on our Way to solve my Problem

By the way - someone told me that i will crash my whole System if i try to install openssl 32 Bit manualy because openssl is a Core Part of OpenSuSe and if i manualy put the 32 Bit Version on it nothing will be like befor

Click to expand...

Then this person shows that he has absolutely no knowledge about ISPConfig and no deeper knowledge of compiling linux programs. Otherwise he should know that you can set different paths during compilation

1) ISPConfig compiles a 64Bit OpenSSL on a 64Bit system
2) ISPConfig does not replace or interact at all with the OpenSSL that is installed by SuSE.

SuSE releases before 10.3 had a package named openssl-devel-32bit that is needed, but it looks that 10.3 does not have this package anymore.

Maybe you can place symlinks to the 64Bit OpenSSL in /usr/lib/ or suse has relaesed a replacement for this package with a different name, as several desktop programs rely on this package as well.

And how could this produce a Problem when ISPConfig uses its own openssl?

Click to expand...

ISPConfig uses its own openssl for apache on port 81 and generating ssl certs. But your problem occured during the php compilation and php in ispconfig is compiled (only on 64 Bit systems) with the openssl from the system.

You can try the following (if there are openssl librarys in /usr/lib64):