domain suddenly stops browsing and displays default cgi page - symfony

i am surprised, domain stopped suddenly browsing and it shows default cgi page.
www.eddsp.gov.np not working properly. but sometimes its content page loads correctly like eddsp.gov.np/contact loads perfectly while cgi error comes in eddsp.gov.np | Again sometimes eddsp.gov.np/contact shows 404 error.
while if same site content loaded from subdomain
eddsp.imagingtrade.com.np
it works fine everytime and in every condition.

I came to know that it's caused by A record. Which are changing time to time. After talking with my DNS Providers. They had corrected it.

Related

iframe in Chrome doesn't work when a 404 NOT FOUND is returned, but does for 200

I have a simple iframe on a page showing a SharePoint library. Don't go telling me to post this over on SharePoint board, ignore that for now.
The page will return a 404 NOT FOUND but SharePoint displays a pretty Page Not Found page (of which we've customized). When this happens, the users cannot see the content of the iframe. Chrome errors with:
Failed to load resource: the server responded with a status of 404 (NOT FOUND)
Once the file has been placed in SharePoint, and the 404 is fixed, then they can see the contents of the iframe.
The big problem is that this is working on my computer, I see the SP Page Not Found error, no one else does. I don't know why. We've since added both the parent site and SharePoint to the Trusted Sites in Internet Options but it still doesn't work. Assuming there is nothing needed to be changed on the HTML of the parent page or SharePoint, what on the client computers need to be changed?

ASP.NET 2.0 website white screen of death

I am encountering a strange issue which is only affecting several users from an over 7000 user-base. Having searched the web for several hours to no avail, I'm hoping someone here can help!
I have an ASP.NET 2.0 website and when certain users try to access the home page (Default.aspx) they receive a white screen with no content loaded. This issue is occurring both in production environment and if I run the solution against a copy of production data. So I am able to replicate the exact same issue when I pseudo the problematic users.
When debugging the application in VS2005 and set a breakpoint in the code behind in the Default.aspx, the breakpoints are fired/hit so I know the request is working. The problem seems to be once the server has finished serving the request, the response back to the client/browser is empty.
Here's another strange thing I've noticed. If I alter the HTML in Default.aspx by adding a new white line or whitespace, the page will load fine for the same set of users. I thought I had resolved the issue with this fix but unfortunately the white screen issue just manifests itself once again.
Within Default.aspx, there's some AJAX requests using jQuery .load function but this can't be the issue because this functionality exists for every user of the site. The only variable is the amount of content returned within this request can vary depending on the user. But why would it resolve itself when I put a whitespace or whiteline in the page and then manifest itself hours later?
Another thing to note is it's only Default.aspx that is encountering this issue. If I browse to another page by typing in a page in the address bar, the page is served OK.
Hope someone can point me in the right direction on how I can debug or even resolve the issue.
It sounds like your ajax is the cause but without seeing some code, it's difficult to know why.
It could be a timeout, or an error that is preventing the ajax from completing it's function.
You need to use a tool like Charles or Fiddler to debug what is happening whilst the page loads whilst logged in as these users. In a nutshell, a tool like Charles will display all the detail surrounding requests made and responses served to the browser, including any failed responses.
I think it has to do with http headers, caching or encoding. But I cannot tell more without code.
Is output caching enabled for this page?
Can you give us the raw http headers for both the request and response?
If a white screen appears, will it be fixed by pressing ctrl+f5?

can not add an iframe tab

Ok, so I've done it a hundred time or more, but today - got a new problem.
created a simple html page with an image
uploaded to a server
opened the page in the browser - no problem, all works fine.
created a new app, selected "tab" and insert the tab name, the http and https url
Tried to view the app and got "The page you requested was not found"
I've checked with other iframe tabs that I've built, they all configured the same, yet the new one - fails to load.
I've seen that the interface has changed a bit, Its not unusual that Facebook breaks things from time to time but maybe I'm missing something?
Edit: also, from some reason I don't have the "View App Profile Page" on that app
They changed some things around, profile pages are no longer being made. Check this out http://developers.facebook.com/blog/post/611/
Although I'm still having problems with getting errors when I try to add the app

Drupal 5 and node?destination=node

I've had a drupal 5 site for over 2 years. For some reason my browser dropdown URL retains www.xxx.co.uk/node?destination=node for the site url. This has work until now - when I get
The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
* This problem can sometimes be caused by disabling or refusing to accept
cookies.
typing in the bare url www.xxx.co.uk gives the same results. I'd just modified the site to add another picture gallery. I can access the site by typing in www.xxx.co.uk/node/1 but if I logout I'm back to the above problem, I assume for the same destination=node problem.
Didn't change any modules that I recall. Any ideas?
OK, I can answer this myself after a bit of investigation. I used import images to load my pics. What I failed to notice was that the nodes created by the import were all set to promoted to front page. Remove this from all the image nodes and everything is back to normal. No idea why my browser dropdown retains the url as above.

website not loading from one location

I have a website hosted at webhost4life.com. It works fine when I load up the website from various locations (home, coffee shop, library, etc). But from my friend's house it will NOT load. It just looks like it's sitting there thinking and the website might load a few images here and there but that's. The full page doesn't load and most of the time nothing loads.
This is a c# asp.net website. My question is, how do i go about troubleshooting to find out what is wrong?
Right now I do not really know where to start. These are the things I have tried:
static page - i uploaded a static html page and that loads up fine!
fiddler - i track the session in fiddler and get nothing back. but when i try the static page i get normal results and it's working fine.
tracert www.mydomain.com - this looks fine, i get similar results with www.yahoo.com
telnet www.mydomain.com 80 - i do this to ping port 80 of the website. if i type "get" and hit enter i see a "Bad request" message but i see the same message for other websites and they work fine from here
ftp - ftp works fast and is fine
So at this point, I know that my asp.net parts of the website doesn't seem to work but only from this one location. It works fine from everywhere else I have tried. But static pages DO work just fine.
Any ideas?
Try doing the telnet 'get' and actually request a page that is having problems. It could be that you are referencing elements in your application that your friend's computer is having trouble connecting to. If you get back all the mark up of the page, then it's one of the items that the page is referencing that is causing the problem. If the page renders incompletely, then your site may be having problems or the might be a network issue between your friend's house and your site. Since your application loads up from other locations I'd suspect that your friend's computer or network has the problem rather than your site. Your site shouldn't care where the request is coming from.

Resources