I am a newbie web developer and I just finished my MERN Stack project. I am trying to deploy it via Heroku as the server handler and at Netlify for my frontend.
In actuality, my website is already up but the problem that I'm having is that I cannot access it on my computer. I can however access it on my mobile phone and some of my friends was actually able to see it on their unit. They already tested it and the frontend is working with the backend successfully.
When I'm trying to access my website on my computer, it just says that I can't access it and says DNS_PROBE_FININSHED_NNXDOMAIN.
I tried accessing it on 3 browsers namely Firefox, Chrome (in incognito as well), and Edge. I also have nothing on my console logs. I tried searching the web for answers but I've tried many things but can't seem to resolve this.
Here's the image link for the error.
If you have any idea, any help would be much appreciated! Thank you very much!
I have created a multilingual Umbraco website which has 3 domain names pointing to it for each language. The site has gone live and people are starting to share links to it on LinkedIn and other social media. I have metadata in the website which should be picked up when these links are shared. On LinkedIn when the link is shared it has 'coming soon' as the strap-line, which is what was in the holding page months ago suggesting the site isn't being re-scraped.
I used the Facebook link debugging tool and that was returning a run-time error with a 500 response code.
My co-worker insists that there is nothing wrong with the DNS and there aren't any errors in the code of the website so I am wondering if anyone has any ideas why the website cannot be scraped?
It also has another issue where one of the domains sometimes doesn't redirect to it's www. version despite have a redirect on the DNS which may be related.
Is there some specific Umbraco configuration that I may have missed? Or a bug within Umbraco that may cause this?
Aside from this issue the website is working fine, it is just these scrapers seem to be unable to hit the website successfully.
Do you have meta data set for encoding? see https://www.w3.org/International/questions/qa-html-language-declarations probably long shot.
I Googled one of our sites today (gamestyling.com) and saw that the results where in Chinese. It looks like our site was hacked but I see no traces of that. When opening the site all looks normaal (no Chinese).
On further inspection it seems that Google doesn't see the website correctly:
I cannot verify in Google search console. When I use the meta tag it shows me it detected a completely different tag.
When running pagespeed insight the preview does show Chinese: https://developers.google.com/speed/pagespeed/insights/?url=gamestyling.com
Also, when running the site through a proxy it looks completely normal.
Any idea how I can get Google to see my site correctly or what is causing this issue?
UPDATE
I now have access to Google search console and found that someone already had access to the property (2nd user):
I cannot remove the user because it uses a meta tag that google thinks is still in the header but doesn't appear in my code. So I'm still not sure if someone is playing tricks on Google or that we've been actually hacked. Note; nothing has changed on the server itself.
UPDATE2
This article describes exactly what's going on; https://blog.sucuri.net/2015/09/malicious-google-search-console-verifications.html. I must say that's an amazing safety fault on Google's part...
I had experienced this issue on one of the site and resubmitted website for review in google webmasters. Search results in google were corrected in couple of days.
Current versions of firefox throw security error even in official Google examples.
Firefox security error in google oAuth login
You can try to open it in Firefox. The official document is here:
https://developers.google.com/identity/sign-in/web/sign-in#add_a_google_sign-in_button
You can find the address of the page with the button itself in the source code of the given page. I wanted to provide it but Stackoverflow was against posting two urls in one question.
I have recently inherited a website written in Classic ASP, and am currently trying to get a sense of the state of things. The website is working in production, however the development environment (hosting on a Windows Server 2003 box) produces an HTTP 500 error when you try to navigate to it.
I realize that HTTP 500 errors just mean that an unexpected server error occurred, and that this also is more than likely the ASP code crashing for one reason or another. I have tried numerous browsers (IE, Firefox, and Chrome) but they all have the same amount of information.
Being primiarly an ASP.NET developer I am use to the yellow screen of death which can be configured to show a stack trace.
So my question is, how do I convince IIS and/or Classic ASP to give me a better hint about what is causing the error?
Update:
I should have gone into more detail originally, but here are some of the things I've looked at.
I've looked at the event logs
(Application, Security, System, etc)
and there is nothing relevent there.
I have looked at the IIS access logs
and I see the access attempts, and
just 500 errors. It is even
producing 500 errors on favicon.ico
If you can't find the offending line by turning off "Show friendly HTTP error messages" as Wayne suggested, then try adding "On Error Resume Next" to the code along with response.write statements. I've found with problems like these, you just have to start going line by line through the code until you find the offensive code.
Just out of curiosity, is Active Server Pages set to allowed in the Web Server extensions in IIS on the dev servers?
Have you checked the Application portion of the web server's Event Viewer for error entries?
What alex said, also make sure that you turn off "Show friendly HTTP error messages" in Internet Explorer and then browse to the site; that tends to give you a more specific error message (although still generic compared to ASP.NET's stack trace) along with the line number.
If you have a global.asa file in your web directory, you could rename the file and try loading the favicon.ico file again. If it loads, the problem lies within the global.asa
Clearly an old question, but for what it's worth, if you have access to the development server (direct or remote desktop), you can access the site from there. Localhost requests reveal more debugging information about classic ASP including line numbers.