Plesk 12.x / Linux :: Standard Domain Forwarding Does Not Forward Https Connections
Apr 29, 2015
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 have re-built a website on a new domain. Now I want to redirect http://www.olddomain.com/anything or http://olddomain.anything to www.newdomain. Because the file structure is totally different, I want all redirections to go to the Home Page of newdomain.
Initially, I used Standard forwarding in the Plesk CP but that attempts to keep the filename the same. So www.olddomain.com/wibble tries to go to www.newdomain.com/wibble. But wibble dies not exist on the new domain.
Should I use htaccess with physical hosting instead on olddomain.com? Is the following correct?:
Will that basically cover any request? Anything that people have saved or which appears in Google searches, no matter whether http:// or http://www.
And for neatness on the new domain, I would like to add www to any request like http://newdomain.com/whatever to go to http://www.newdomain.com/whatever which I think means that Google analytics will report more accurately.
So would my htaccess file on newdomain.com be like this?:
I want to add a subdomain foo.bar.com to a master domain bar.com in the subscription bar.com. Normally this works but if I set the hosting type of the master domain to forward, I cannot add subdomains anymore. If I have already added a subdomain, I cannot change the hosting type of the master domain. Also it is not possible to add a second domain to the subscription anymore.
With the standard-DNS-Layout every customer has an MX-entry like MX 10 mail.customerdomainexample.com
The problem is, that inbound mailservers get a TLS warning, because the mailhostname does not match mail.companydomainexample.com, which is the domain with a valid SSL-Certificate pointing to the same server.
Wouldn't it make sense to change the default template to mail.companydomainexample.com since it is the same machine anyway?
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.
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 update my plesk 11,5 to 12.And I activate (limit control for smtp)After this action the email forwarding fails in all domains of plesk.This is the mail system at host fsyc.org. You can delete your own text from the attached returned message.
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?
Many of our clients create e-mail accounts that forward incoming e-mail to mailboxes hosted on other e-mail services. e.g., Gmail.
Lately, though, a handful of these accounts have been receiving a lot of spam (i.e., UCE) and that's been causing a lot of damage to our reputation with these other e-mail services because the message that's being forwarded appears to have originated from our servers.
Code: <email@example.com>: host gmail-smtp-in.l.google.com[220.127.116.11] said: 552-5.7.0 This message was blocked because its content presents a potential 552-5.7.0 security issue. Please visit 552-5.7.0 http://support.google.com/mail/bin/answer.py?answer=6590 to review our 552 5.7.0 message content and attachment content guidelines. g20si28780491ici.46 - gsmtp (in reply to end of DATA command)
Is there some way to...
Find accounts that are configured to forward to gmail?
Disable forwarding in accounts that are configured to forward to gmail?
OK, I am confused. I have one domain that is parked on top of another domain. I would like Mail that comes to the parked domain to be automatically forwarded to the same user name at the primary domain.
Can I change a DNS or MX record to facilitate this?
how to use Plesk through “Customer's Guide, Plesk 12.0” manual from Odin website. I have a VPS Cloud plan at OVH with Plesk 12 Web Admin + CentOS 6.6
I wish to know how to enable POP3, IMAP, SMTP, FTP protocols with a cryptid connections using native Plesk/CentOS certificate (not purchasing one but self-made by the server). Moreover, I wish to know if it uses SSL or TLS.
Since the update I have a problem with my Firewall. I need to set "Allow all incoming connections" under "Server => Firewall" in order to connect over FTP with TLS (explicit). This was working before the update without allowing all incoming connections. How to fix this in the Plesk panel?
My Customers and I have Problems connecting to IMAP-Server. By moving through IMAP Folders I get the Massage "Unable to connect to your IMAP server. You may have exceeded the maximum number of connections to this server"
I know this Article: [URL] ... and all the other related to this issue.