Founder of AECNU Computers 1993 and AECNU Computers & Internet 1998 specializing in Web Hosting wpmu-hosting.org and webhostingvirtualdedicatedservers.com and many other telecom related services.
Member since March 2011
Not a WPMU DEV member?
Sign up today and get access to 140+ plugins and themes, plus 24/7 support and private member forums!
aecnu commented on Domain Mapping to either http or httpsJan 20, 2017
Following up as I see a potential issue that could be easily mitigated ... Martin is using .htaccess to force SSL but I am not sure this works for the graphics and other items within the theme ... if it does I would like to know of this. If not, though depending on how the theme or coder adds the graphics and content ... we ourselves use WP Force SSL which we found on the themes we have used does the job not only forcing SSL but also using secure URL's for the graphics etc. as well. WP Force SSL is a free plugin available in the WordPress repository https://wordpress.org/plugins/wp-force-ssl/ Joe :-)
aecnu commented on Domain Mapping to either http or httpsJan 20, 2017
Greetings Gentlemen :-) Part of the answer is indeed Martin no longer has a dedicated IP as he added a second entry to his IP being a dev site that then changes the dedicated IP to a shared IP ( but still only shared exclusively by his hosting account ) by said action and therefore the behavior as described above regarding "A" records sending a domain at the server that the server does not know about and the server cannot resolve - therefore the symptoms of not resolving correctly to the WordPress MultiSite installation. When using a dedicated IP the server actually does not come into play and WordPress itself resolves the DNS in the "A" record type setup to the applicable subdomain/subdirectory site. Being that we are the hosting company involved I know exactly every in and out of these MultiSites and servers of course and we can certainly take care of Martin by moving his dev site off the formally dedicated IP and make the IP once again dedicated to just his MultiSite ... but this in itself will present several other challenges ... For example going https:// on the addon domain in an "A" record DNS environment WITHOUT making an alias or addon domain entry means each and every domain that uses SSL ( https:// ) will require a purchased SSL certificate to be created and installed. I say purchased due to the fact that unless the server has appropriate DNS entries itself one cannot take advantage of our FREE SSL certificates that are now automatically issued and assigned to every domain added to the server which includes both alias and addon domains. Now I am strictly referring to Domain Mapping and not the MultiSites main domain which can be either subdomain ( use a purchased wildcard SSL certificate ) ~or~ subdirectory/sub folder which our systems will automatically add a Grade "A" SSL Certificate in association with cPanel and Comodo themselves. So the choices are as follows ... A) Unsecure - Going only http with mapped domains - no problem and the dedicated IP is the solution even if the main MultiSite domain has the applicable SSL certificate installed - the MultiSites subdomains ~or~ subfolders will still work as secure with a https:// URL but not the domain mapped domains. But for SEO and security this would not be good ... see below. B) Secure https:// URL's for mapped domains - In this scenario to get the mapped domain secure and to work correctly Martin or client/end user will need to pay for SSL certificate first creating the applicable CSR which is then submitted to the SSL certificate supplier and then in turn the SSL certificate supplier will send an email to the domains registered owner to authorize the SSL certificate. When the SSL certificate is authorized by the registrant which is usually as simple as clicking a link ... then the SSL certificate is issued and sent to the purchaser in which then needs to be manually installed on the server which Martin certainly has the access to perform. Then every year when the certificate expires the same procedure must be re-enacted including the CSR and manual installation. Now lets compare this to the other option which is a whole lot simpler, requires the least amount of interaction by all concerned parties and what I recommend which providing for the least expense and manual labor/intervention ... whereas option B above requires much more interaction not limited to but including interaction of the admin and the client/end user of approving the certificate and certificate installation ... C) Secure https:// URL's for mapped domains the client proceeds as normal sending the domain to the MultiSite installation using the "A" record method. Martin manually adds the mapped domain to his cPanel either as a addon domain ~or~ alias ( formally called parked ) resolving to /public_html The SSL Certificate is automatically added to the domain by our systems FREE without any further interaction by either the administrator nor the client/end user. These FREE SSL Certificates also auto renew themselves so that portion is also removed from the equation. This is far more efficient and less costly even IF Martin decided to charge a nominal fee for the "secure" URL version for manually adding the domain to the server as a addon on or alias taking only a minute or two to perform and most likely cheaper then the cost of a SSL Certificate not to mention the hassle of creating and submitting the CSR etc. etc. Furthermore considering that the Google Chrome Security team announced the Chrome browser will begin labeling HTTP connections as insecure starting in January 2017 and that HTTPS:// secure sites are also rated higher then non secure sites as reported in the WPMU DEV newsletter referring to the WP Tavern article https://wptavern.com/chrome-to-add-security-warning-to-http-sites-beginning-2017 - it is my opinion that NOT making all the sites forced SSL is a disservice to the client/end user and to said clients/end users visitors and it appears Google agrees considering they are the ones that are marking sites secure or not and giving further ranking to secure sites versus unsecure sites. Secure sites obviously improve the user experience by not only encrypting the transmissions between the two but also security wise in the perspective that hacker injections to date are almost always to an insecure domain making the injection super obvious in a secure environment which would then indicate it is insecure making the injection stick out like a sore thumb making detection and mitigation easy peasy. With the big picture at hand ... with all the above realized and factual - it is my opinion that Martin and his cleints/end users would be best served forcing SSL on everything, using the fact that "all sites are secure with FREE SSL certificate" as an advertised or mentioned feature would please the potential client/end user and everything secure would get the SEO secure ranking bonus ... and all Martin needs to do is add the "A" record mapped domain to his control panel as either a addon domain ~or~ alias/parked domain to achieve all of the aforementioned. Joe :-)
aecnu commented on Multisite issue : 404 error when I add new sites?Oct 21, 2016
Greetings JAEJ :-) Are you logged into the installation and going to network administration to try and install plugins? In a multisite there is only o...
aecnu commented on Multisite issue : 404 error when I add new sites?Oct 19, 2016
Great reply Lakewood! But also she should reset permalinks which is done by simply clicking on save in the permalinks section. Notes Regarding adding ...
aecnu commented on easiest way to add a second domain with email to a main multisite domainJul 01, 2016
Greetings All :-) I am going to address this ticket with common sense and the fact that this client said he has a dedicated server - https://premium.wpmudev.org/forums/topic/easiest-way-to-add-a-second-domain-with-email-to-a-main-multisite-domain#post-1103379 Now tell me how is the host or cPanel responsible to support plugins even if it is not a dedicated server? Um - NOT! But of course we still try to help our hosting clients if we can. Next and primarily the client here is trying to domain map a TLD domain to another TLD domain - he is clearly using the wrong plugin ( multi domains plugin ) which adds an alternate domain to the MultiSite to create sub sites using said domain - but has nothing to do with mapping a TLD to another TLD within the same MultiSite in which he is clearly trying to do as mentioned in his original post. "We want to add a second domain to http://aresnyc.org . In other words if someone types in http://nycdistrictares.org it will load up http://aresnyc.org for SEO and non Dup purposes redirect to http://aresnyc.org and still have email with http://nycdistrictares.org Cpanel Account by the way" The answer to this is within his original post and troubleshooting as indicated in his original post the site was working just as it should - and the answer is he should be using domain mapping. If domain mapping cannot map one TLD to another TLD he should then be domain mapping the "new" domain to the same sub site that he mapped the original domain. If that does not work he should then map the "new" domain to an arbitrary sub site of the multisite, make a arbitrary post and then use a redirect ( perhaps https://wordpress.org/plugins/quick-pagepost-redirect-plugin/ ) to the original site/domain. The clues were in his original post with the main clue being "This is what the url looks like http://aresnyc.org/wp-signup.php?new=nycdistrictares.org" That line alone shows that the domain is correctly making it to the target multisite with or without a dedicated IP and a clear indication that the "new" domain needs to be mapped ~or~ redirected using one possible method that I described and there are several other ways to effect the redirect. In summary: The client should remove the multi domain plugin as its function is not related to the task he wants to perform. He should then either domain map the "new" TLD to the original TLD and if that is not possible create an arbitrary sub site ... map the "new" TLD to the sub site, make an arbitrary post (static as front page ) and then use a plugin like https://wordpress.org/plugins/quick-pagepost-redirect-plugin/ to redirect said post to the original TLD. Have a GREAT upcoming weekend everyone! Joe :-)
aecnu commented on WPMU Hosting and Joe's teamFeb 27, 2016
Greetings Everyone :-) I thought I would chime in with some of the facts dispelling some of the myths that Johnny had already begun to bring to light ...