Plesk 12.x / Windows :: Custom Hostname Not Redirecting To Https
Feb 3, 2015
I have a VPS with 1&1 and i'm trying to customize the Control Panel hostname to mypcp.mycustomdomain.com...I have added mypcp A record for mycustomdomain.com pointing to the server's IP address.
Right now if I type the full URL: https://mypcp.mycustomdomain.com:8443 it works fine but if i type just mypcp.mycustomdomain.com:8443 it keeps loading until it times out but it never redirects to https.
the hostname is www.domain.com also in the serversettings of plesk. When we go to http://www.domain.com:8443 we become redirected to https://www:8443. The only way to connect to plesk is to use https the redirect from http doesnt work.
I keep hearing that redirecting from http to https is not very secure [non-SSL to SSL]. Among other reasons, one reason is that the browser may continue to think it is communicating with non secure server and may not encrypt the data. Is it true? I hope not, I am using the following -
A few months ago we had upgraded our server from Win 2k3 with Plesk 8.6 to Win 2k8 with Plesk 11.5.30 migrating all the domains. After migrating, all the domains are working fine, but when trying to access the control panel using a specific user we get always the error "the page isn't redirecting properly" in different browsers, login in with Admin user it works perfect, or even with a different domain user.
Tried already to change the subscription to a different owner and get it back, it didn't work neither on the different owner or the original one.
Does HTTPS on a Windows site require SNI like it apparently does on Linux nodes? If it does, I've been avoiding moving a site to an existing server that only has one IP, so I may as well move it there instead of setting up a Windows node in PPA.
I have a Reseller client that has a custom app that requires a virtual directory with special permissions. The app uses a MS Excel add-in as its front end on the user PC. Is there a way to register and publish this app for the resellers web sites without have to create the folder and set the permission by hand?
I have install Plesk 11.5.3 on my Windows Server 2008 r2. I want to try Mailenable on the PleskServer, so i installed the feature, but know when I am calling the webmailer with http:webmail.domainname.de works fine, but when I try https://webmail.domainname.de i become a Not found: HTTP Error 404. The requested resource is not found
Current Version Installed :Parallels Plesk Panel 11.5.30 Update #31 Problem: When username have @ like : email@example.com
Steps : When configure the setting all go right (test to validate setting is ok too) , but when Scheduled Backup Settings using Personal FTP Repository cannot connect for server because the url use 2 @ like error message below.
Error Message : Cannot parse output file 'ftp://firstname.lastname@example.org@mydomain.com/' [Invalid URI: Can not parse the hostname.]
I have set up an Apache web server that has ssl enabled. If I go to https://myserver.com I get the 'it works!' page and the certificate is valid and trusted. If I go to https://myserver.com/myapp that also works (it's an Oracle weblogic deployed java app that I'm fronting with Apache).
I would like to configure Apache so that when a user goes to simply https://myserver.com it automatically directs them to https://myserver.com/myapp rather than showing the 'It works!' page. I have read some documentation and experimented with setting a redirect via the https.conf file and even the ssl.conf file but nothing seems to work. I either get a 404 or simply the 'It works! page.
We will be migrating from plesk 9 to plesk 11 and I am having some trouble finding a fix for something. Previously, http and https could either share a directory or have split directories (httpdocs and httpsdocs) for a site. Now all I see is httpdocs and I can't find a way to have separate directories.
I have Plesk 11.5 installed on my server. There are about 30 sites on the same shared IP address. I need to set up a site to be accessible via https://<ip-address-of-the-server> . According to the documentation I went to Setting -> IP Addresses and selected the desired site from the drop down. Now http://<ip-address-of-the-server> (note, 80th port) works like a charm. Unfortunately https:// displays only the first page of the selected site; all CSS, JS and other files are not found (404).
I did some research and found that Nginx forwards the requests to Apache for all the PHP files and tries to handle all the static files by itself (what is expected and correct). But it looks like that there is no special configuration for nginx which would specify where to get these static files for the IP address, and Nginx just uses the first loaded config (started from b in my case).
I temporary resolved this issue by modifying the last_nginx.conf for the desired domain this way: listen XX.XX.XX.XX:443 default_server ssl;
Note I added "default_server" directive. Of course it would be erased on each reconfiguration of the config files, but as for now I do not see how I can put it in custom nginx.conf or on the server servel level. I reckon Plesk should include the directive in the file the same way as it produces last_httpd_ip_default.conf Apache config for the selected domain. It looks to be an easy fix on the template level, may be I will do it later, but for now this is just the bug report.
I am currently with MediaTemple and my hostname is automatcially as.mydomain.com, they have told me that the as is deprecated now and I can chose what to put for the hostname... Do I just put www is that how it works?
I find it easy to update softwares (PHP, MySQL, phpmyadmin, Apache, etc.) in Directadmin because they have integrated custombuild. I plan to try Plesk for the first time, what is the counterpart of custombuild in Plesk?
URL....We are running Plesk 12 on a Linux VPS where we have multiple domains running.Multiple of these domains should redirect from www. domain name. ext to https://ext.domainname.com.This is configured with the Domain forwarding in Plesk, with hosting type Forwarding.But as described in the 2 links provided above, whenever you go to https://www.domain.ext, it does not redirect, and actually shows a Security error, since the domain doesn't have the SSL-certificate installed (because it should redirect to the https://ext.domainname.com).
Clearly we don't want visitors on the website to receive the (incorrect) Security error, and we want all traffic to http(s)://www.domain.ext to be redirected to the appropriate subdomains. allows us to redirect both the https/http connections to the domains, without forcing us to have the domains have a Website hosting add redirect them manually with (for example) .htaccess.
I migrated domains from another server and they had separate http and https folders. Now I need to make them use same httpdocs for both http/https. How do I do it for a single domain? How do I batch do it for all domains?