Why does ownCloud 9.0.1 install on shared hosting fails? - ssl

I'm trying to install owncloud 9.1 on a shared hosting (kreativmedia) but i get the following error:
Error
ownCloud is NOT installed
download of ownCloud source file failed.
SSL: certificate subject name '.owncloud.com' does not match target host > name 'download.owncloud.org'SSL: certificate subject name '.owncloud.com' > does not match target host name 'download.owncloud.org'
I've tried to change this two option in the setup-owncloud.php file to FALSE
if (Setup::isCertInfoAvailable()){
curl_setopt($ch, CURLOPT_CERTINFO, TRUE);
}
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, TRUE);
but whit the same error.
I've tried to download the files via FTP, and to run the installer, it failed whith this error:
Error
ownCloud is NOT installed
The selected folder seems to already contain a ownCloud installation. - You cannot use this script to update existing installations.
I have no admin rights on this server, just a Plesk 12 access. Any idea?

I have the same problem. I opened the script and I found url https://download.owncloud.org/download/community/owncloud-latest.zip
Tried in web browser and it downloads fine. Also tried without HTTPS.
So open the file setup-owncloud.php go to line 139 (or search for https://download.owncloud.org/download/community/owncloud-latest.zip) and replace https with http. Upload modified script to the server and try again.
It worked for me.

It's looks like you catch temporary SSL certificate's issue with download.owncloud.org:
'.owncloud.com' does not match target host > name 'download.owncloud.org'
Now there everything fine with https://download.owncloud.org but it's forwards to owncloud.org

Related

Bitnami SSL bncert-tool failed for Gcloud

I am trying to renew my SSL Cert on Gcloud VM Instance SSH with Bitnami. But it's giving me the
"Please type a directory that contains a Bitnami installation. The default installation directory for Linux installers is a directory inside /opt."
every time i run the bncert-tool
I have followed the steps to try and revert to backup files as directed in this post (thinking i might have did it poorly last time) I copied the backup file to the bitnami.conf and httpd.conf but I still get the same error.
Copying contents of the backup file is this right?
Please help, my ssl expires in 15 days! Is it not easier to just get SSL Through Wordpress plugin? Is it possible to remove this Bitnami SSL Completely?

How can install and configure IBM HTTP Server v9 from archieve zip

I want to install the "IBM HTTP Server for IBM WebSphere Application Server V9.0" without the IBM InstallationManager just with an archive file.
I already downloaded the archive file 9.0.5-WS-IHS-ARCHIVE-win-x86_64-FP003.zip
and just run the postinstall.bat and I cannot install it .
So, Does anyone know how can install it?
This the message that get everytime i run this command
postinstall.bat
postinst: Could not reliably determine the server's fully qualified domain
name, using 127.0.0.1 for ServerName
SERVERROOT_NATIVE=D:\Mohamed\Mohamed Nour\MohmedNour\Software\IBM WAS
ND\IHS
SERVERROOT=D:/Mohamed/Mohamed Nour/MohmedNour/Software/IBM WAS ND/IHS
PORT=80
GSK7LIBDIR_NATIVE=D:\Mohamed\Mohamed Nour\MohmedNour\Software\IBM WAS
ND\IHS\gsk8\lib64
GSK7LIBDIR=D:/Mohamed/Mohamed Nour/MohmedNour/Software/IBM WAS
ND/IHS/gsk8/lib64
SERVERNAME=127.0.0.1
postinst complete
here when access IBM HTTP Server
click to view errors picture
and also after register IHS in Admin Console and created unmanaged node for remote
when am access application from WAS it success but not when access through IHS
and also updated the http.conf configuration like :
<IfFile plugin/config/webserver1/plugin-cfg.xml>
LoadModule was_ap24_module C:\Program Files\IBM\WebSphere\Plugins\bin\mod_was_ap24_http.dll
WebSpherePluginConfig C:\Program Files\IBM\WebSphere\Plugins\config\webserver12\plugin-cfg.xml
</IfFile>
and also web server created from console named webserver12
Just did what you want.
This is the procedure:
Download 9.0.5-WS-IHS-ARCHIVE-win-x86_64-FP003.zip
Unzip to target folder (recommended folder without spaces in the path)
Run postinstall.bat it displays the following:
D:\install\WAS_90\IHS>postinstall.bat
postinst: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
SERVERROOT_NATIVE=D:\install\WAS_90\IHS
SERVERROOT=D:/install/WAS_90/IHS
PORT=80
GSK7LIBDIR_NATIVE=D:\install\WAS_90\IHS\gsk8\lib64
GSK7LIBDIR=D:/install/WAS_90/IHS/gsk8/lib64
SERVERNAME=127.0.0.1
postinst complete
Verify in httpd.conf that you have settings changed, for example search for server root settin: ServerRoot "D:/install/WAS_90/IHS"
Add IHS as service (you must have Administrator command line to do it):
httpd.exe -k install -n IHS9A
if you dont have admin rights just start server with the httpd.exe command
All done. Access your server via http://localhost
To federate to WebSphere App Server just follow usual instruction and provide your IHS unzipped folder as IHS install root.
To configure your plugin add the following lines to httpd.conf, the plugin file for IHS is located in IHS\plugin\bin. Example for Win:
<IfFile plugin/config/webserver1/plugin-cfg.xml>
LoadModule was_ap24_module plugin/bin/mod_was_ap24_http.dll WebSpherePluginConfig c:/IHS/plugin/config/webserver1/plugin-cfg.xml
</IfFile>
These lines were correct after unzipping the IHS, but you manually messed that up, pointing to non existing C:\Program Files\IBM\WebSphere\Plugins folder. While configuring IHS in WAS console you have to think and set the IHS home (eg. C:\IHS) and Plugin home (c:\IHS\plugin) correctly to the directory where you unzipped the IHS archive. This was already discussed here Archive Installation for “Web Server Plug-ins for IBM WebSphere Application Server V9.0” instead of IM

Digital Ocean CyberPanel (on Ubuntu 18.04): ACME certificates blocked forbidden - 283 Failed to obtain SSL for domain. [issueSSLForDomain]

I installed a brand new DigitalOcean droplet using a marketplace base (so on paper everything should be OK out of the box).
When trying to issue certificates, i am getting this error:
[11.13.2019_04-48-28] /root/.acme.sh/acme.sh --issue -d thehouseinkorazim.co.il -d www.thehouseinkorazim.co.il --cert-file /etc/letsencrypt/live/thehouseinkorazim.co.il/cert.pem --key-file /etc/letsencrypt/live/thehouseinkorazim.co.il/privkey.pem --fullchain-file /etc/letsencrypt/live/thehouseinkorazim.co.il/fullchain.pem -w /home/thehouseinkorazim.co.il/public_html --force
[11.13.2019_04-48-28] [Errno 2] No such file or directory [Failed to obtain SSL. [obtainSSLForADomain]]
[11.13.2019_04-48-28] 283 Failed to obtain SSL for domain. [issueSSLForDomain]
[11.13.2019_04-48-34] Trying to obtain SSL for: thehouseinkorazim.co.il and: www.thehouseinkorazim.co.il
I checked and UFW is not installed.
I do have a network firewall but it is the same one as another droplet that does allow for certificates (same rules) so I think it is not the cause.
I searched all the answers online and no luck.
I even installed certboot to manually issue certificate but same error (i did it because I know you need to register initially to get certificates and I haven't so I thought it was the cause).
Any ideas? Thanks!
update: i did a clean droplet again, this is the issue without anything I did manually:
Cannot issue SSL. Error message: ln: failed to create symbolic link '/usr/local/lsws/admin/conf/cert/admin.crt': No such file or directory ln: failed to create symbolic link '/usr/local/lsws/admin/conf/cert/admin.key': No such file or directory 0,283 Failed to obtain SSL for domain. [issueSSLForDomain]
I checked and there is no folder "cert" under "conf" in the path written above.
There's an known SSL issue on recent version due to some environment/code changing. We already aware it and submitted a new version which has that issue fixed included. Please give it a day or two and you should be able to launch the new version from marketplace which comes with CyberPanel v1.9.2.
Best

XAMPP 7.0.4 PHP 7 LDAPS Connection can't bind LDAP works fine

My connection to our Domain Controllers via LDAP is fine however when I try to connect via LDAPS it fails to bind. I've added the c:\OpenLDAP\sysconf\ldap.conf path and file and tried adding this "TLS_REQCERT never" to that file as several sites have suggested but no luck.
The code I'm using is the same as below modified for my environment
<?php
$con = #ldap_connect('ldaps://the.ldap.server', 636);
ldap_set_option($con, LDAP_OPT_PROTOCOL_VERSION, 3);
ldap_set_option($con, LDAP_OPT_REFERRALS, 0);
var_dump(#ldap_bind($con, 'user#sub.domain.com', 'password'));
?>
Just wondering if anyone else has come up against this issue and found a way around it at all?
Got the cert from the DC,
I created a c:\openldap\sysconf folder, added the following ldap.conf file:
#--begin--
# Instruct client to NOT request a server's cert.
TLS_REQCERT never
# Define location of CA Cert
TLS_CACERT c:\openldap\sysconf\trusted cert.pem
TLS_CACERTDIR c:\openldap\sysconf\
#--end--
put the trusted cert in the location I listed in the file and restarted XAMPP and it was happy.

sending email with PHP sendmail not working for primary domain

example.com has a web server and a mail server.
Email sent from the web server to any email address (except #example.com) works.
Email sent to #example.com works from any other source.
Web server is setup to use webmail. The web server is Ubuntu 12.04 with Apache and PHP
Any help appreciated. Thanks.
=== edit
This fixed the problem, thanks
https://serverfault.com/questions/65365/disable-local-delivery-in-sendmail/128450#128450
Apache was trying to handle the email locally on our server. When I looked at the log response I saw it was returning the following error.
User unknown
550 5.1.1 recepient#example.com
After following these steps the email was routed to the correct mail server. My setup is Ubuntu 12.04 with PHP 5 Apache2 and Sendmail.
Edit the sendmail config file on the Apache server:
sudo nano /etc/mail/sendmail.mc
At the end of the file add the following lines of code to handle email correctly:
define(`MAIL_HUB', `example.com.')dnl define(`LOCAL_RELAY',
`example.com.')dnl
Save the file and exit.
Update the sendmail setup in the command prompt:
sudo sendmailconfig
Follow the steps, I said yes to everything
Restart sendmail:
sudo service sendmail restart
Try sending the email again. It should work now.