I have read about everything about this situation and had very different recommendations and read many differents scenarios from 2007 to 2010. But nothing exactly like my case even here on stackoverflow, so I'm here to ask the real experts. Considering this:
website1.com
- hosting: simplehelix
- domain name: simplehelix
- main magento installation (1.3.2.4)
- SSL installed
- paypal PRO (credit card taken directly on this site)
website2.com
- hosting: none
- domain name: goddady
- DNS/nameserver: to simplehelix servers
- folder called /website2/ that loads magento
- paypal PRO (credit card taken directly on this site)
website3.com
- hosting: geohost
- domain name: geohost
- DNS/nameserver: to simplehelix servers
- folder called /website3/ that loads magento
- paypal PRO (credit card taken directly on this site)
All 3 sites share most of the same products (80%) because they are 3 real physical businesses from the same owner having mostly the same products. They use one Magento admin for products, categories, customers, sales.
QUESTION: Now, in 2011, I'd like to know exactly what is the simplest, easiest, fastest way to have SSL on website2 and website3 so that all our transactions are secured? Can I just buy SSL on godaddy and geohost and install it there on the domain names and it will work even if the DNS is pointing to simplehelix? Do i have to reinstall magento on 2 new hosting plans + ssl and not be able to share same database?
Note:
- we do not want to share carts
- we want people to stay on the respective websites
- we want to use paypal pro
- keep cost down
- please be clear on your steps/description, as this might help many other people more/less technical
Thank you for your help
Joel
I'm not sure how you've had different recommendations. The answer is simple: you'll need to buy an SSL certificate for each of your domains that you want secured.
Sharing a Magento installation, talking about the DNS, etc, is not relevant.
Buy the SSL certificates, get your webhost (it looks like you're using SimpleHelix for hosting all of the websites) to install them all for you, then change the secure URL in the Magento admin for each of your stores (use the dropdown in the configuration area to change the configuration scope from Global to each store in turn) to the appropriate URL, presumably https://www.website{1,2,3}.com from http://www.website{1,2,3}.com.
Easy :)
Sounds like you need to think of Magento terminology 'stores' or 'websites' - with 'stores' you can have lots of them on the same SSL, sharing the same checkout. However, if you have built your sites with 'websites' then you cannot have them all go to the same checkout and you will need multiple IP addresses.
It is relatively simple to move your hosting to a VPS that supports more than one IP address, although check before you leap. It is also possible to move your 'stores' to a single 'website' in Magento.
Ok, it seems that the easiest way to do this was to buy 2 new hosting accounts at my hosting provider and then buy SSL on both and ask them to redirect to the Magento installation. It worked, but it cost 2x hosting account that I do not use at all...
Related
I guess that's a very simple task, but I can't manage to have SSL work on gitlab pages. Gitlab pages documentation is too vague for me.
For example, when they say "Make sure your domain doesn't have an AAAA DNS record." does that mean the subdomain (say gitlab.mysite.com) doesn't have a AAAA record. Or does it mean my whole DNS configuration shouldn't have such a record?
Also if that's the later, how can I manage to make this work?
Maybe someone has a source to a good tutorial for this because I really struggle finding simple information (not assuming any prior knowledge about SSL/gitlab).
I just went through the whole process beginning to end and set up a GitLab Pages website on a custom domain with a Let's Encrypt certificate -- it worked like a charm.
I had to:
a) set up a TXT record to verify domain ownership, and
b) add an A record to point at the GitLab Pages IP address (since my domain DNS management provider didn't allow me to set up a domain-level CNAME)
After this, GitLab went and fetched a Let's Encrypt certificate for my Pages web site.
I didn't have a AAAA record, so that didn't come into the picture.
As per GitLab Pages documentation section GitLab Pages integration with Let's Encrypt,
Caution: This feature covers only certificates for custom domains
Issue 3342 is open to add support for sub-domains.
If you are still having trouble, let me know, I'd be happy to help with this.
I’m trying to get my head around a problem and hoping for some clarity
I have built a basic LAMP site running on a VPS.
My client also has a site built on WIX (online website builder)
I would like to get both sites running under the one domain name. Perfect solution would be (though I don’t believe is possible):
example.com - WIX
example.com - WIX
example.com/y - LAMP
example.com/z - LAMP
My next idea would be to use subdomains:
www.example.com - WIX
xyz.example.com - LAMP
Is any of the above possible when trying to work with WIX and LAMP setups without spending lots of money on something like nginx? Or do I just have to use different domains?
I am not familiar with WIX ecosystem but I think that the path of least resistance is to just setup a subdomain using DNS records.
Refer to your DNS manager, but basically you just want to add an A record.
Your DNS records might look like
example.com. A 1.2.3.4
www.example.com. A 1.2.3.4
So you will just need to add
xyz.example.com. A 5.6.7.8
If your DNS records are managed by WIX, I found the proper documentation.
By the way, Nginx open source is free. Nginx plus is a paid service that includes some goodies on top. Blog post Feature comparison
I have looked all over the internet and I can't a reasonable way to make my web-server running on apache go live with an unique ip and everything. How would i got about making it live and viewable for other people?
Normally you would not do this. You'd buy a hosting account from some provider like GoDaddy, BlueHost, etc. and put your software there, and make it visible that way. Making your localhost server viewable would involve buying a static IP, which is not cost effective for most people.
I suppose it depends on what you mean by "go live" if you need it to host a specific domain name then yes - get a shared hosting account somewhere ~ if you just need access to it and it does not matter what the domain name is, you can use something like DynDNS: http://www.dyndns.com/services/dns/dyndns/
-sean
Right now there's two different accounts, with both domains having each their own hosting account,
for similar website (let's say domain.fr and domain.co.uk)!
I've merged the two websites into one (currently hosted as 0.0.0.0/site/language ),
making it multilanguage! The script just need a prefix on root,
such as like www.domain.com/english/ or www.domain.com/french.
This works as expected, if only a domain is used, but I would like to use two different domains (domain.fr / domain.co.uk).
So, I want to catch the current request URL, to know what language to display. What's important is that, the request urls keep persistent.
For example,
http://domain.co.uk/language_english
http://domain.co.uk/language_english/somepage.php
http://domain.co.uk/language_english/somedirectory/someotherpage.php
While,
http://domain.fr/language_french
http://domain.fr/language_french/somepage.php
http://domain.fr/language_french/somedirectory/someotherpage.php
This two domains are actuall hosted in same hosting account, let's said
127.0.0.1/language_variable/somepage.php
Any suggestions or good practices?
If I got your question , It's a feature in Web Hosting's solution which is called Addon Domains and depend on hosting company that how many Addon Domain they let you to put into one account !
I currently host my company's website and blog on separate servers, reached by separate domain names - www.example.com and www.example.net. This is so I can give blog server access to our partners without compromising security on our main server. However, our SEO guy is now demanding that the blog be put on our main server, as www.example.com/blog.
I would like to maintain the current server separation rather than putting both on the same server. Is there any good way to keep them separated, but have them both under a single domain name? A subdomain would also be acceptable (blog.example.com).
My main website server is a Debian box running Apache 2, and I have full root access to it. The blog server is run by Hostgator, and I have limited access.
Edit: Thanks, all. In this particular situation I don't particularly want to transfer the blog again, and I don't have easy access to the DNS records, so i went with mod_proxy and it worked like a charm. I wish I could give you all "preferred answer" status, though, because all of your information was awesome.
A subdomain would be easy: just create an A record in DNS which maps blog.example.com to the IP address of the blog server, and have another A record in DNS which maps www.example.com to the main website server (this latter record probably already exists).
Would the SEO guy be happy with blog.example.com? It's not the same from an SEO perspective, but it might be good enough for him. I work at a company where SEO is at least 1/3 of what we do, and that's our setup: blog.example.com and www.example.com.
You could try to get fancy and proxy requests to /blog to the 2nd server, if you insist on keeping the blog off your box, but I think you can find a secure way to share space. Proxying like that could get annoying, and it basically doubles the latency to your blog.
Give the blog guys an account on your box; don't give them root/special privileges. If you can get away with it, don't even give them SSH access -- just give them a FTP login (make sure they can't access /var/www), and maybe a mysql account or something. (As you can see, this all depends on how much control/power the blog folks demand.)
Then, just make a symlink to the blog root, so they can write to a restricted area like /home/blog/www and still have it included in the website:
ln -s ~blog/www /var/www/blog
If a subdomain is for some reason not a possible way for you to go, you could use Apache's mod_proxy module to proxy requests to /blog to your second server.