I'm using OSX and I have been using AMPPS for my local development environment. Everything was peachy then all of
This site can’t be reached
This site on the company, organization or school intranet has the same URL as an external website.
Try contacting your system administrator.
ERR_ICANN_NAME_COLLISION
I've tried to automatic proxy config in network preferences, restarting my computer, restarting chrome etc.
Turns out .dev is top level domain and purchased by google so can't be used even locally...:\
Related
Working in the local environment I'm quite often getting errors on communication between the visual studio, IIS, IIS-Express and the browser (any combination). Everything is working on closing down the computer and doesn't any more when the computer restarts. Problems have started when the computer joined the domain.
I've spend hours searching for a solution to the problem. It looks as Widows Defender is to blame which is triggering different rules after I've joining the domain. It is enough to switch off the firewall, start any web application and enable the firewall. Simple (yet annoying) but working (what is most important).
I've just started using homestead to try and do some laravel development on my windows machine (normally I work with valet on mac which does all this for you) and it looks like when I start a new homestead box (using "vagrant up") it automatically sets up ssl? And chrome is freaking out when trying to connect to the website because the certificate is invalid.
I'm not sure how to get around this problem, how can I prevent the homestead box from trying to use ssl out of the box? Or get chrome to accept the cert that it's trying to provide?
I've tried downloading the certificate (crt file from /etc/nginx/ssl on the box) and installing it on my machine and then restarting chrome but I get the same error.
As #brianforan has pointed out in his comment, Google has decided for their own reasons that the latest versions of Chrome will no longer support development under the top level domain of ".dev". Chrome will assume that any .dev domain is automatically meant to run under SSL, and will redirect to SSL.
Use an alternate TLD for your site - I have a preference for .local or .localhost myself, but it's entirely up to you.
I installed a Microsoft Navision Demo Server on my machine recently for testing/research purposes. When trying to work on one of my websites I noticed that when I browse to http://localhost/ ; this welcome page is being shown, does anyone know how to remove it? I have removed all Sites in IIS Manager but that hasn't helped. When I browse to 127.0.0.1 I get to see my own website that I am working on though.
Deleting the sites from IIS Manager actually did do the trick. It was a matter of clearing the cached localhost website from my browser.
I have recently installed subversion and nginx server on my machine (macbook pro). I'm fairly new to subversion as a whole and have just built a single webpage through this version control system, and now I'm faced with the task of testing it in all of the relatively modern web browsers. My biggest concern, as far as browser compatibilty is concerned, is Internet Explorer which, in order to test, I need Windows. I have Windows 7 installed on my mac via Virtual Box, and herein lies my problem.
I have not committed the new page I've just created to the repository, by the request of the client. Because of this, as far as I know, I have no URL to use for testing in IE Tester, Firefox for Windows, etc. How can I test this 1 page site's browser compatibility with without having committed any changes to the repository?
I can test it easily on my machine using MacOS, by just typing in local.*.org and it shows up. Again, windows is my issue. This project is due this Thursday (5/24/12), so you're help is greatly appreciated.
1) Developing and testing your web page is different from managing your web page source. In other words, testing web pages != using SVN.
2) If you've not actually been able to use SVN yet - and if your client has no preferences - then please try TortoiseSVN:
http://scplugin.tigris.org
3) Please post back any specific questions you have about installing/using SVN.
If the site uses any scripting languages like PHP, and/or databases, you need to get those setup correctly first. If your website consists of just HTML/CSS/JS... then you can access the website via either of these methods:
Enable Web Sharing (System Preferences > Sharing > Web Sharing). Then type in the IP shown there into your browser in VirtualBox and it should load. (This is probably easier than trying to get nginx configured, though it might very well load if you just type in your machine's IP.)
In VirtualBox, select your VM (powered off), Settings > Shared Folders. Add your website's root directory. Launch the VM, then browse to it within the VM and open up your files there for testing.
My current environment is setup like this:
- Local dev machine with git & SVN
- Remote DB server
- Remote web server
- Web server mounts local dev machine's www folder as a volume and serves the PHP pages from there
- Load web browser in VMs or any other machines. Edit hosts file if need be for local routing.
I have several windows shares hosted on a PC running Win7x64. This machine is also hosting a basic website via IIS7. Whenever I deploy a new copy of the website to IIS any WinXP users connected to the shares on that machine get disconected.
After some period of time (20mins or so) the shares all start working again.
This only seems to affect WinXP clients, with them recieving this error message described here: http://support.microsoft.com/kb/890413.
The resolution provided by Microsoft works, but it means that everything I deploy a new copy of the website all of my users have to go through this hassle.
Any IIS experts out there know what is happening, or how to resolve this?
Thanks