Deleted wrong domain in Google reCaptcha v2 - recaptcha

I have two similarly named domains that use reCaptcha.
I wanted to delete the unused domain.
I went to google/recaptcha/admin.
I deleted the wrong domain.
So now I can't access the domain.
Is there a way to restore deleted domains?
If not, how else can I get access to it?

I got back in by going to the hosting platform and deleting the recaptcha folder from the plugins folder for the domain.

Related

Deceptive site ahead | Laravel app deploy on cpanel

Here is the screenshot of this.
Few monts ago I deployed my this laravel app in cpanel. But Now when I'm accessing the site it shows me this message... I think it is hacked or malwared added in the app.
Can anyone tells
what are security steps? should I have to follow for deploying the project in cpanel securely...?
How can I protect my app from attackers in cpanel?
What I missed on basic think in my app was APP_DEBUG was false I have to set this to true.
Except this is App_Debug:
Is there any security should I follow...
Or should I have to move shared hosting to dedicating hosting..?
This has nothing to do with your hosting or your APP_DEBUG setting. In fact never set APP_DEBUG to true on a live website this can leak all your environment variables including database credentials to the world
Here's an explanation from the google site:
Social engineering is content that tricks visitors into doing something dangerous, such as revealing confidential information or downloading software. If Google detects that your website contains social engineering content, the Chrome browser may display a "Deceptive site ahead" warning when visitors view your site. You can check if any pages on your site are suspected of containing social engineering attacks by visiting the Security Issues report.
In your case it may be because either (as you said) the website was hacked and this content injected in it or (less likely) there is content you added to the site that Google is interpreting as misleading (either because it is or because it looks like it is even though it is not).
The remedy here is explained by the above linked site (wont include the entire text just a gist but do check the entire Google site):
Check in with Search Console
Remove deceptive content
Check the third-party resources included in your site
Request a review
If your page has been hacked then you should probably just delete everything, change your passwords (all of them) reset the app key and re-deploy it. Also contact your shared hosting provider to tell them what happened in case they need to be aware of any vulnerabilities or credential leaks.

Website not working on root domain with https

I am trying to deploy a NextJS website to Heroku or Vercel and add a domain name to it using https://www.names.co.uk.
Adding the domain works but for some reason I cannot access the website at https://my-website.com, however I can access it with http://my-website.com and https://www.my-website.com. I need it to work for this url 'https://my-website.com' as the website is already ranked in google with this URL. I was wondering if anyone had any idea of how this can be done. Please ask if you need more information.
Apologies if I have posted this in the wrong place.
Thanks in advance.

Heroku app custom domain points to empty root

I've set up my app on Heroku. Everything loads fine when I access the herokuapp.com domain.
I've added my own domain to the app and added the CNAME as instructed but when I go to the subdomain it's just showing an empty root.
I'm not sure what I am doing wrong here!
I've checked the domain is added to the app running heroku domains in terminal and it's there.
This is the first time I've published an app on Heroku but I've followed the instructions and I can't see what the problem is.
Any help is much appreciated.
Thanks
I managed to resolve this issue by adding another CNAME record in the domain provider account and creating the subdomain in there, rather than from the server.

Letsencrypt domain validation fail on Parse.com hosting

Letsencrypt domain validation requires folder with dot in it like .well-known/acme-challenge but Parse.com hosting's public folder deploy ignores folders with name start with dot char.
Dot character seem to be mandatory for the ACME verification.
Parse.com team should consider supporting folder name with dot to support Letsencrypt. Time being I wish to know any other alternative solution.
This is a odd workaround but might work if Parse.com allows you to issue redirects
Let´s Encrypt client will follow http redirects so you can redirect it to another place which contains the .well-known challenge. You might have to run it in standalone and put challenge by hand at the other place but it will work. You can try to redirect it to S3 bucket on Amazon AWS for instance or to your own PC running a miniserver.
But I don´t know Parse.com and if they support you to configure http redirects.
good luck.

Giving someone access to an addon website on my server

I need to give someone access to a website I made for a friend but only want them to have access to the addon domain folder. Is this possible (with JustHost)?
Figured it out. In case anyone was wondering, in the control panel on JustHost there is an FTP Accounts section where you can give access to certain addon domains such as public_html/domainname.com with its own login.

Resources