How to add your localhost website to google recaptcha domain list. My domain name is localhost:8888/folder/index.php
When adding the above domain name you get "URL starts with an invalid scheme" error.
To add the localhost to reCAPTCHA domain list you have to be careful in following steps:
Remove http:// or https:// from the url.
Also remove the www. from url.
Do not add port number (e.g. localhost:8000)
You can just add localhost or 127.0.0.1
if you want to add your site (e.g. http://www.example.com) then just add example.com
You need to get at least a free DNS and point it to your localhost. Google does not allow non domain names to be used.
What you can attempt to do is create an api key for another valid name and see if it works. They have been tightening down on api keys and I have seen a lot of keys no longer work that were used across more than one ip/domain.
All sub directories are not valid. Once you have a domain name pointing to the subdirectory then by default it will work across all sub directories of that domain name. Same applies to SSL.
I'm getting an error "Localhost is not in the list of supported
domains". This was working before, what should I do?
localhost domains are no longer supported by default. If you wish to
continue supporting them for development you can add them to the list
of supported domains for your site key. Go to the admin console to
update your list of supported domains. We advise to use a separate key
for development and production and to not allow localhost on your
production site key.
1: Create a separate key for your development
environment
2: Add 127.0.0.1 to the list of allowed domains
3: Save changes and allow up to 30 mins for changes to take affect
For anyone trying to get Recaptcha (especially invisible Recaptcha) working when they have javascript disabled except for specific whitelisted sites: this actually worked for me. Just add [*.]localhost to the javascript whitelist.
Related
I have a domain name which i need to to point to a sub domain of my existing website. Both the domain name in question and website are held with the same host so i have CPanel for the website (which has its own domain name and is currently online. Note the host does not provide CPanel (or similar) for domain-names only (i.e. without hosting).
I have seen subdomains and addon domains but from the description in CPanel i cant figure which if either will do what i want ... or even Aliases.
How can i point the domain name to a sub-domain? if possible. I do not want the existing websites domain name to appear in the url when visiting the sub-domain pointed to by the new domain name.
Thanks.
Since you're using cPanel... https://documentation.cpanel.net/display/ALD/Setup+Edit+Domain+Forwarding
If you just deal with a registrar instead of a provider, typically you point '#.domain.com' to 'http://sub.domain.com' - where #.domain.com represents the direct name, domain.com.
I'm running Magento on a shared server with a single IP. I originally set it up as a single store with no plans to do multi-stores. Do I need to have store codes trailing each domain in magento to get this work correctly? They will all checkout at the main store URL. I have done this in the past and it has worked fine for me, but I was using store codes and with this instance I am not.
Will it completely jack up my SEO?
So I have store1.com (main store) and store2.com which needs to checkout at store1.com
Any help or link to a how to would be great. Have not been able to find a straight forward answer.
Your proposed setup of having store1.com and store2.com with a shared checkout URL of store1.com will work with a bit of work from yourself, but it's not clean or ideal in my opinion. Magento will append an SSID every time it switches domain to try and re-load the customers session data (They will have ?SSID=something). You would also need to change the checkout URL in your templates to only use the 1 domain which would require hard coding the full URL to the checkout and cart page in the store2.com templates.
Personally I would simply have separate checkouts for each domain which is supported straight out of the box in Magento without really doing anything. Why the need to have the checkout always under 1 domain? If it's because of SSL and 1 IP limitations then buy a UCC SSL certificate for multiple domains and have all the domains required to run on the server setup as SANS on the certificate. Cheap and simple. This way there is no need for store codes in URLs, SSIDs in domain switching, and the user will always stay on the same domain without any funny switching business or complications.
As a customer I would also be a little surprised to shop on one domain and then checkout on another these days, especially if one of the domains is international and this will ultimately effect your conversion rate.
You seem to be familiar with store views, so once you have setup your secondary store view, simply go into the admin and override the base URLs for the secondary domain. Point the store2.com domain to the same IP address you are using for store1.com. Setup a vhost on the server so store2.com effectively replicates the vhost for store1.com. You can use vhost directives so that magento initiates the correct store view for the relevant domain name in your new vhost.
SetEnv MAGE_RUN_CODE yourstorecode
SetEnv MAGE_RUN_TYPE store
You should now be able to have multiple sites/domains running on 1 magento instance each with an individual checkout URL. e.g. store1.com/checkout/onepage/ and store2.com/checkout/onepage/.
By using a UCC SSL certificate, the SSL will be valid for both domains and not cause you issues so no need for multiple IPs.
I am trying to deploy my app on Openshift.
I've added www.mydomain.com, and mydomain.com as aliases on Openshift and changed the cname record 'www' to myapp-mydomain.rhcloud.com
when I try to access the app these are the results,
myapp-mydomain.rhcloud.com - Opens myapp
www.mydomain.com - redirects to myapp
mydomain.com - opens a blank page (the source of the blank page links to a godaddy's parking
looks like this http://mcc.godaddy.com/park/xxxxxxxxxxxxxx
how can I make my mydomain.com point to the application at myapp-mydomain.rhcloud.com
I have tried to change the 'A' record of the domain that pointed to 184.168.221.xx but it needs to be an IP address not the app address.
thank you so much for any help.
Not sure if you've seen this Openshift Article or not https://www.openshift.com/blogs/custom-url-names-for-your-paas-applications-host-forwarding-and-cnames-the-openshift-way but it will walk you through step by step on how to acheive exactly what your asking.
The important part to pay attention to is:
If you want to forward over your whole domain, such as mycompany.com
and not www.mycompany.com, then you either need to use Domain
Forwarding or find a DNS provider that allows "Naked" CName records.
Domain forwarding uses a web server to do a redirect.
Also be sure to check out https://www.openshift.com/forums/openshift/domain-with-no-www-dns-question-is-that-possible.
CloudFlare allows you to create naked domains as CNAME records for free. Add CNAME records for both mydomain.com and www.mydomain.com which aliases myapp-mydomain.rhcloud.com.
I have the domain test.com(just as an example), which I have bought from namecheap. I have redirected the domain to http://app-test.rhcloud.com/. However, when entering test.com in my browser I still can see http://app-test.rhcloud.com/ in the browser instead of test.com. Any recommendation how to clean that up?
I appreciate your answer!
You need to use a cname for your application, not a redirect. A redirect just tells the browser, now go to this domain instead. Check out this blog article for the correct way to setup what you are trying to do: https://www.openshift.com/blogs/custom-url-names-for-your-paas-applications-host-forwarding-and-cnames-the-openshift-way
When a new user signs up, many sites create a new domain, something like newuser.example.com
Does this mean that they have separate directories for every user, and copy the code base into the newly created directories and create sub domains? What is the best way to do this?
Refer here:
When you auto-create subdomains on user signup does it create a new website or gives appearance of a website?
Surely a DNS rule of * -> IP address would take care of adding the subdomains quickly. Then its up to the web server to deal with the different host headers.
I would then create a new Apache directive for each different host header I needed (one for each subdomain) and have them be aliases for real website.
You can setup a wildcard domain *.yourdomain.com and handle the differences within your code if the application is pretty much the same between subdomains. Everyone comes to the same application and you just parse out the subdomain and store it in a variable which can be used to lookup different data in your database and / or render different templates / themes, etc.
I.e. subdomain_fu