I created a new Azure Web App (web site) on the path https://todoangular1-b-nschou.azurewebsites.net and I tried to access the Kudu Debug Console by inserting 'scm' between the application name and the domain name. Like this:
https://todoangular1-b-nschou.scm.azurewebsites.net/
However, the site is not available.
Some more research showed that the error was caused by a failing DNS resolution. I then added an entry to my hosts file pointing todoangular1-b-nschou.scm.azurewebsites.net to the same ip-address as todoangular1-b-nschou.azurewebsites.net and suddenly it worked.
My own conclusion is that the Azure platform did not properly add the new DNS-name under the scm.azurewebsites.net zone. Did anyone else experience this odd behavior?
What probably happened is that there was a small delay in DNS propagation. But if you try hitting the site before that, you would then be affected by DNS negative caching on your machine, which can last a little while. My guess is that during that time, if you had tried to access it from a different machine that didn't have the negative caching, it would have worked (and it works fine now).
Related
I have been running a gitlab instance and today I was trying to setup the pages function. I followed the gitlab guides and google cloud docs, it seems my config file got corrupt or broke (by me ofc) and even the ssh was down (directly on google console) till I rebooted the VM. Now I'm able to see that the instance is working on the shell but can't get it back online, I have 3 options here, 1) I wait a day or so to see if this is a domain/dns issue, 2) keep trying to a recover the gitlab that only had 3 users and no projects, or 3) make a fresh one and try to setup everything well from the start. The only things bothering me is losing 2 users that came to my project organically.
What can I do here? I'm trying to fix the config file but at the same time I don't know if its a domain issue because I had to change some dns configs to set the subdomain. The only thing I cannot understand really is how or why did my shell went down for at least a hour after I changed the configurations for gitlab. And btw are snapshots the right way to make backups with gcloud ?
What can I do here?
Undo your changes; in other words, put things back they way they were before, when the system was working. To do that, you have to know exactly what you changed.
If you are not keeping your config file in version control, you should start to do that, as that will make it easier to track and control your changes.
I decided to answer my question since I know how this problem occurred and it may occur for others.
Conditions:
Have a Gitlab self hosted.
Try to setup DNS settings for Gitlab Pages and the URL stop
responding even if the Gitlab instance still runs on the machine.
Here we can see the problem was in the DNS setup.
In my case I setup different DNS cases in my DOMAIN service DNS settings. Instead this DNS setup have to be made in your HOST/SERVER side.
To properly make a Gitlab DNS:
the wildcard domain *.mydomain.com type A should be on the server config, in my case gcloud DNS. Find out the software you use for your main machine server config.
Its good practice to setup the domain and server without redirection and set the proper DNS on the DOMAIN settings. This way your domain will resolve the subdomains without need for redirection on the DOMAIN settings. Once you set a wildcard type A record you can or cannot make the subdomain as a CNAME example, subdomain.mydomain.com. or you can use a separate IP for the subdomain with a type A record.
In summary, when setting up Gitlab Pages DNS do not change your DOMAIN settings, change your SERVER DNS settings.
I have a Node project running on a Windows server using IISNode on a Windows virtual machine.
Everything worked fine up until a few days ago when the VM underwent a Windows update, and now the site isn't serving any files.
When I start the server, there is no indication of anything being wrong, but when I go to the URL, I get the message:
www.mydomain.com didn't send any data
ERR_EMPTY_RESPONSE
Initially, when I was checking all the settings, I noticed that when I clicked 'Test Settings' under basic settings, that there was an authorization failure saying it cannot verify access to the source code directory.
But when I changed it to connect as specific user instead of application user, the error went away but the above issue was unchanged.
This makes me think it could be a permissions issue, but I've granted permission to the App Pool, IIS_IUSRS and IUSR, so I could be wrong.
I've tried multiple solutions on StackOverflow, including this highly rated one with no luck.
Any help would be appreciated.
Annoyingly, I found the answer a few hours after placing the bounty.
The problem was that it didn't have a static IP address, so when the VM was updated it was on DHCP and so was allocated a new IP, hence the website stopped working.
We had CrushFTP installed on an Azure 2012 VM that recently died, so to speak. We wound up spinning up a new VM and reattaching the original data disk to the new VM.
After configuring IIS for the web portal part of CrushFTP, and cleaning up some script errors on the landing page, which is now on a 2016 VM, we get an HTTP 405 error when trying to log in to CrushFTP.
I checked to make sure the VM accepts POST requests - it does. The confusing thing is when I check the browser console, it's saying the server is NOT accepting POSTS, and this is happening both on our company network and from outside the network. I can see from our work network it's an issue with our proxy server, but from my mobile device outside of the network, I see the exact same rejected methods.
Any ideas? I don't have a whole lot of code to share since CrushFTP is a black box.
EDIT: I think the IIS setup was a red herring. I was going off some notes from a former co-worker who set this up, but I don't believe she set it up in IIS.
From what I'm reading, the CrushFTP HTTP server needs to be exposed as a public app through port forwarding in the VM. Whenever I run Crush locally on the VM, everything works fine. But since I set it up in IIS it hasn't worked.
I figured it out. I had to add an "Allow" entry of POST in IIS.
i am using azure webapp with microsoft auth.
has been working fine for months.
however today it is broken.
the login.microsoftonline.com page is failing with css and js loading errors.
ie Request URL:https://secure.aadcdn.microsoftonline-p.com/ests/2.1.7415.7/content/cdnbundles/watsonsupport.min.js
is failing with a
SSL_PROTOCOL _ERROR
i tried raising with azure support but i cant login into the azure portal as it also uses login.microsoft.com page.
anyone able to help?
-lp
I have found a solution to my version of this problem. I am in Australia, my ISP is Telstra and I have a NBN connection. I do not have a proxy server.
I found changing the DNS servers from the Telstra default servers (61.9.194.49 & 61.9.195.193) to Google's DNS servers (8.8.8.8 & 8.8.4.4) fixes the problem. If the DNS servers are changed back, the problem reappears. Changing the DNS back to Telstra reintroduces the problem. Changing them back fixes the problem. (You must flush the cache each change).
Hope this helps - but can only speculate as to why. Microsoft have accepted this as the solution to my problem and closed the support case.
The problem no longer exists when using the Telstra default DNS.
I suppose the take-home message is to remember your ISP sometimes caches stuff, mostly a good thing, but on the rare occasion causes problems.
I've recently ported to a different hosting company (VDS), and on the new server, installed IIS 7.5 Express, latest versions of PHP and MySQL.
I then copied the files from the old server to new server (NOTHING beyond the content of the folders of my websites, so no config files or anything except the web.configs in the sites themselves), set-up websites. I've tried to visit a website, and I got a 503 Service Unavailable message, tried both remotely and locally at the server, no change.
Tried on every site, even on Default Web Site, and no change: still 503.
I've checked the permissions to the folders of the websites (and all the children), and both my account, Network Service, Administrators have effectively full control of all the contents.
All the apps run in DefaultAppPool, which runs under ApplicationPoolIdentity. Tried creating a new app pool, moving sites there, no luck, tried setting "Load User Profile" to False in pool settings (read it here HTTP Error 503 on IIS 7.5 after SP Install), no change.
The event viewer in an extremely detailed way says:
"A process serving application pool 'DefaultAppPool' terminated unexpectedly. The process id was '2356'. The process exit code was '0xfffffffe'."
and nothing else. Five times of this error, and the pool is shut down due to rapid protection. I restart the pool, try again, nothing changes. No matter I'm trying to get an .aspx, .php, or static content. Here is the most weird part: when I set the app pool to run under LocalSystem, it works. No problem. But everything else fails.
I've checked the website folders about ten times, changed, erased, re-added rights etc tried everything but no change. It's as if there is another file that I'm forgetting to check that the pool's user is unable to access. But the event viewer does not help me. This started with the new server and I tried after installing everything, so I can't tell after what this started happening. I obviously won't be running under LocalSystem. Even my own user, Administrator, doesn't work.
The only identity that works is LocalSystem. My user, LocalService, NetworkService, ApplicationPoolIdentity all fail the same way. I'm going crazy, I'm 99% sure this is a user-rights issue. But all the website files are accessible, and I haven't changed anything in the system32 inetconfig or anywhere.
Ok, found my own answer again.
The process w3wp.exe runs under the DefaultAppPool user, not NETWORK SERVICE. I don't know why it doesn't run under NETWORK SERVICE, but after some research it turned out that the process needed access to C:\Windows\System32\inetsrv\config\schema and giving NETWORK SERVICE access didn't change anything. I've by coincidence found somewhere about the DefaultAppPool user, gave read permissions, and by starting the pool, all my websites started working perfectly. Quite weird, I always thought that the IIS processes ran under NETWORK SERVICE by default, and I'm sure that I haven't changed any setting.
Try running below commands with some changes
appcmd set apppool /apppool.name: <YourAppPoolHavingIssuesHere> /managedRuntieVersion:v<.net Framework version here>