There is a problem on my system as I am using WAMP server. Some time i need to refresh page 2-3 time then it works otherwise it gives "could not connect to server" something like this errors.
I have searched a lot and have checked many thing like SKYPE which is not installed on system IIS is also not installed reinstalled the wamp etc. Is there any other solution for this issue?
Related
We recently did an update to 2016 for ColdFusion. After the update my application was not working. It shows Access Forbidden error. I checked the WS.config file to see if ColdFusion and IIS are connected. At that time I could see it was empty. When I tried to add it then it shows the error All the IIS sites are already configured by some other version of ColdFusion.
Can anyone please help me with this problem?
We got the error message All the IIS sites are already configured by some other version of ColdFusion. when switched to another Coldfusion version. We tried many of the solutions which didn't work out for us.
Finally, we uninstalled IIS windows feature entirely(we were able to do that since it was a dev machine) restarted as prompted, and installed IIS feature again which resolved the problem.
my new created django project working fine with this information
Django version 2.1.7, using settings 'django_server_api.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CTRL-BREAK.
running fine
then i opened in one browser is loaded quickly working quickly.
but if i open same local host in another browser it is taking more than 5 minutes, i dont know what is the issues? may be django is like this? or do i need to change any config in the setting,py file ?
Some browsers (Firefox) has a problem browsing to localhost on some Windows machines.
You can solve it by switching off ipv6, which isn't really recommended.
Using 127.0.0.1 directly is another way round the problem.
Note : If there are heavy media is can also slow downs django
I recently opened Wamp server after a long time I didn't touch it. It was fine back then, but when I try to open Wamp server now, I get an error that says
The application was unable to start correctly (0xc0000142).
In addition, the wamp icon is orange, while back then, it was green.
I have tried to search for a solution on the internet, but I wasn't able to find.
I have also noticed that when I try to open phpMyAdmin, the page says
#2002 - No connection could be made because the target machine actively refused it.
The server is not responding (or the local server's socket is not correctly configured)
But i'm able to open my localhost start page (the one with the loaded extentions list).
Thanks for helping.
Same error after creators update 1703 (Windows 10).
Error: httpd.exe was unable to start correctly
Error code: 0xc0000142
I'll do a quick google search and see what this is about. I will get back for sure.
UPDATE: SOLUTION
WAMP has released a cumulative update to fix this. It is strongly encouraged that you apply this update after you’ve installed WAMP.
Wampserver update 3.0.8. Sourceforge.
Once you apply this fix, you will be able to start (Apache) WAMP normally.
Actually this error relate to Windows Firewall.
You can go to "Control Panel\System and Security\Windows Firewall\Allowed apps" after that click change settings and in Allow apps and feature find "Appache HTTP Server" and check public then click OK.
Verify your Windows Firewall Services is not running.
I faced the same issue after installing 64bit Wamp. While installing I was not prompted to allow http daemon by the firewall service.
Unsure what to do, I installed the 32bit Wamp & the firewall service prompted me to allow the http daemon.
Wamp started showing green!!
I have installed sql server 2008, mongodb and I tried installing a sitecore instance, but for some reason I can't navigate to any pages on the site. I checked my sql database and iis and it looks like the installation went through without any errors, but I just cant seem to navigate to the site. Any suggestions?
EDIT:
After the installation it asks to launch the instance, which I do. When I navigate to YOURSITE/sitecore the page doesn't load and just says "The Page cannot be displayed" standard IE error message when the site cannot be resolved.
Make sure that you have your site in hosts file. However I wonder why it could be absent there. As installer and SIM should modify it.
E.g.: for site "testinstance" you should have next record:
127.0.0.1 testinstance
(Using Windows 7, Python 3.4, and Django 1.6, using virtualenv)
Hey, all. I tried using django-secure to force https and ssl on my django project. Then I decided I didn't want it until I actually put the site online, because I didn't have a security certificate, so I couldn't even try out the site on my computer. After removing the django-secure code from my settings, uninstalling django-secure using pip, and restarting my computer, any browser I visited the page with while using django-secure forces https whenever I run that particular django project, but not on other projects. Uninstalling and reinstalling worked for Safari and Firefox, but not for Chrome. I couldn't uninstall Internet Explorer or Opera using the Control Panel, so I thought it might be easier just to change some settings in the browsers, if I knew how to do that. Does anyone know how I can make Chrome not force https on my project and how to do that with Opera and IE without uninstalling them?
I think the above details could lead to finding the answer, but if you want it, here's my detailed description of what I did in what order:
I followed the installation and usage instructions at https://github.com/carljm/django-secure, up through "Set the SECURE_HSTS_SECONDS setting to an integer number of seconds and SECURE_HSTS_INCLUDE_SUBDOMAINS to True, if you want to use HTTP Strict Transport Security." I then tried it out on chrome and found out I needed a security certificate, and decided I'd rather wait till I actually put the website online. So I removed the parts of the settings file that I had added following the django-secure instructions, stopped and restarted my local server, opened it on chrome, and found that it forced https, but only for that particular django project. I then used pip to uninstall django-secure, but chrome still forced https. I tried it on firefox, ie, opera, and safari, and had no problem. I then restarted my computer, but that didn't solve the problem. So I reinstalled django-secure using pip, and repeated the steps I had followed from the django-secure instructions. I then ran it on safari and ie, removed those lines from settings, and reran it, and they continued to force https on that django project. I repeated the process with Opera and Firefox, and had the same problem. Uninstalling and reinstalling Safari and Firefox fixed the problem in those browsers. It didn't fix the problem in Chrome. I couldn't uninstall Opera or IE from the control panel, so I think I'll just wait till I find out another way of fixing the problem.
Clear your browser cache.
Django-secure sends a HttpResponsePermanentRedirect (302 status code) to the secure version of the page, so your browser will cache the response and always redirect you to the https version.