My MAMP install on my local mac has suddenly stopped working.
By stopped working I mean that I can no longer access any of my sites nor can I load the MAMP WebStart page. I cannot access PhpMyAdmin either. All attempts to any of the pages result in the following:
The server at localhost can't be found, because the DNS lookup failed. DNS is the network service that translates a website's name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network.
I have had MAMP installed on my machine for almost two years without a single problem.
I upgraded the OS to Yosemite a few days ago.
Now today it was working fine this AM and now at 9AM I can no longer access any of my sites or the start page to diagnose the problem.
The MAMP interface to start/stop servers is accessible and it shows and allows me to start and stop the servers.
What I've tried:
Changing the port ids
Upgrading MAMP to the latest version
Nothing I have attempted thus far has worked.
Has anyone ever experienced this and if so how did you resolve the issue?
Somehow my etc/hosts file had been completely wiped clean.
Not sure how or why or what caused the file to be blown away.
Luckily I had a copy to restore from.
After the restore everything is once again functioning properly.
Thanks to #emrys57 for the tip to look here: DNS Lookup failed - Error with all browsers
Cheers!
Related
Recently i have re-installed my GitLab application on my Linux system. When i tried to access my GitLab application link (https://gitlab.domain.com) on Windows system's Firefox browser i am getting below error.
Since the certificate generated freshly it was conflicting with existing/previous certificate, So i have followed this Link workaround. However even after system reboot also same error occurring, I can't access my GitLab application on Firefox browser.
I'm able to access it on Chrome browser without any problem.
Please let me know still where i need to clear the old certificate to make it work on firefox?
That seems to be the same error as in issue 435013 reported 13 years ago (and still open), where Firefox has an issue with routers and NSS (Network Security Services) (error -8054)
As I understand it, and from the discussion on #312732 which is the underlying issue, the problem is that the crypto uses the cert ID as a unique key in a database.
When a dupe is encountered, you can't have two primary keys in a database, so it just dies with a fatal error, hence FireFox gives up connecting to the site and passes on the fatal error to be presented.
This is not a "fundamental NSS design issue", it's a political issue, Firefox is ACTIVELY refusing to let people access their network equipment.
Check also the firmware of your router:
It seems to me that it is VERY EASY for the server-side products that
generate these certificates to more-or-less fix the problem in updated
firmware with very little effort. Even simply randomizing the serial numbers
in the certs, they would nearly completely eliminate the problem, AFAICT. In
fact, it is worth making sure that the affected server-side hardware has
up-to-date firmware, because some vendors might have already fixed it on
their end already.
Possible workaround (which would work even after FF restart)
This is hardly any fix, but I installed a new Mozilla from scratch on a VM under Virtualbox.
I than browsed to all my local systems I was getting this error. On connecting from the new Window3s sytem running on VM to each local IP, I received the warning, and created the exception.
I than went in to Preferences>Advanced, and Exported all the certificates to a share on one of my NAS units.
I proceeded back to the broken Mozilla running on my Mac OS X 10.11.1, and I Imported all the certificates.
I then restarted FF, and connected to each device I was getting the error on, and I received the "This is an untrusted connection, Get me out of here, or would you like to create an exception." YES!!
I created the exception, and finally I could get to my firewalls, and all other local devices.
Other workaround:
Run: firefox --no-remote --ProfileManager
Create a new profile there.
Open a new instance of Firefox using the new profile. To run Firefox with the profile you can use the command from 1. or: firefox --no-remote -P profile_name
Do the actions there as if it was a separate installation of Firefox
I downloaded the latest version of Appium from the GitHub. I have installed it on two Windows PCs,
On first one it works fine.
But on the second one, just by clicking "Start server v1.7.2" a window appear showing "The server is stopped".
What is wrong with the configuration?
I found the solution for above error.
It was due to firewall modified by an antivirus, it disables all open ports on this PC.
There can be around three solutions:
Format the PC will help us to get open ports, but it is not a recommended solution.
Uninstalling Antivirus can open blocked ports, by recovering firewall to its original state.
If the 2nd solution does not help then Uninstalling Antivirus and create a new User Account on PC, helps me to run Server successfully.
Good morning!
My Xampp has been working fine till a few days ago.
i can access localhost/phpmyadmin - i see my db/tables all intact!
BUT i cant access localhost/ like i used to. it says connection reset.
when i try to access my application thru 127.0.0.1/ the site is not displayed as it is supposed to. images are missing and formatting is out. but i do know my php scripts are working since the menus are being correctly displayed and i am able to log in.
i dont use skype but i do have teamviewer and mu torrent
any ideas will be appreciated
I had the connection reset problem but I fixed it out by:
Disconnection from my WiFi
Uninstalling and re-installing the XamppServer
Checking if phpMyAdmin works (it did in my case)
Re-connecting to WiFi and enjoying the internet :)
Hope it might help
Can't run Pritunl client anymore. It just keeps showing the same error on my Mac.
Error: Unable to communicate with helper service, try restarting
OS X: El Capitan 10.11.6
Tried restarting and re-installing the app.
The app used to work, not sure when it stopped working as I update most updates which come up in app store.
Has anyone experienced this before? Any suggestions on the solution are appreciated.
After some researching I couldn't find anything useful to resolve the issue but I was sure there was a process which was conflicting with functionality of this client. I decided to Quit applications through Activity Monitor one by one. I quitted two or three known to me applications before stumbling upon a service which didn't take up much memory or CPU resources, called helpd. After quitting that application Pritunl Client started without any issues.
What worked for me:
echo "127.0.0.1 localhost" >> /etc/hosts
and then restart
(I had cleaned /etc/hosts previously and it became a problem)
im having troubles making WAMPserver work.
Im currently running Win10.
Firstly I installed WAMP and it wouldnt go green, i googled and found that I should disable some windows features - World Wide Web Services specifically.
After I did that WAMP went green but localhost or 127.0.0.1 isnt working. Additionally I cant open any other website except facebook.com.
Im getting error no server response. Even when i turn off WAMP and stop all of its services problem with browsing remains.
Only fix is restart of PC.
So I cant use localhost and it kills my dns. Anyone got some hints what to do?