In short, I can create a new MAMP Pro 3 host with success and then download and install Wordpress 4.0 via MAMP Pro's "Extra's" feature also seemingly with success (no errors, ) ...yet it doesn't turn out that way as the browser says, "Error code: ERR_CONNECTION_REFUSED".
Full Details: Hi, I've just installed MAMP Pro for the first time on Mac OS 10.9.5 with all the default settings, the WebStart page loaded in the browser, php looks to be running fine. The problem I'm having occurs when running a preliminary test of MAMP by trying the Extras feature and installing Wordpress 4.0. I get no indication that anything went wrong with the default install yet clicking the button next to the Server Name "Open the hosts web page in a browser"... I am greeted with an error in Google Chrome, Firefox, Safari, etc....
"This webpage is not available. Google Chrome's connection attempt to was rejected. Error code: ERR_CONNECTION_REFUSED
Google Chrome's connection attempt to testwpextra.dev was rejected. The website may be down, or your network may not be properly configured.
Check your Internet connection
Allow Chrome to access the network in your firewall or antivirus settings.
Check your proxy settings
"
I'm not using a proxy, I am running apache as my local user and have confirmed the document root is owned by the same user (with read/write permissions), I turned off firewall/littlesnitch just to be sure, same result in various browsers.
I read some fella saying something about setting up his host with IPv6 but I'm using the MAMP control panel to manage the process for me and don't see settings of that nature. Maybe this is done via the Extended tab with directory or VirtualHost parameters, I don't know... wish I did. Please help! Thanks!
I solved my problem by changing MAMPs ports from the default 8888 etc... to 80,443,3306 (on MAMPs General tab). Now all my includes are broken because MAMP doesn't allow "php_value" in htaccess files...one step at a time i guess. =]
Related
We suddenly started seeing this "Could not create SSL/TLS secure channel" error.
Our website does a simple POST to another server to a HTTPS URL
This suddenly stopped working
Nothing has changed (Windows Updates, our updates, server settings) to cause suspicion. That we know of, or can remember.
We can navigate to the posted URL just fine.
We have other websites that also do this same POST to that same server and they continue to work. Everything is using TLS 1.0 and the target server has not changed anything recently. Nobody has turned off TLS 1.0 on either side.
This issue is discussed in many other stackoverflow postings, so to research systematically we made a clone of the website on the same server. Just copied its code (compiled code folders) and set up another virtual host in the same IIS.
The POST operation from the clone works! Same server, same code, same IIS. So we can't even reproduce it on the exact same setup. The copy is working but the original is throwing this error.
So finally the question:
Does the fact that the copied website can POST successfully give anybody any insight into what may have happened?
Could some IIS settings on the original site been changed? The only thing different is they are two virtual hosts on the same server.
Windows Server 2012R2, IIS 8.5, ASP.NET/C#.
I found the solution here:
https://social.technet.microsoft.com/Forums/en-US/9dfb4d09-8096-40c9-ac75-1e23f75417c9/frequent-event-id-36888-windows-schannel-errors-in-the-event-viewer?forum=W8ITProPreRel
The causes can be many, apparently, even Windows updates. Still seems odd that it would happen (consistently) on one website and not on its clone (also consistently).
The specific steps to fix were:
In Group Policy Editor (run: gpedit.msc), went to Computer Configuration > Administrative Templates > System > Distributed COM > Application Compatibility and enabled "allow local activation security check exemptions"
I have been learning the Laravel framework and I used Laragon to get started. Laragon sets up my web server and my Hosts file so that I can access my work through the browser. Normally, I would boot up the server using the fancy "Start" button in Laragon and then go to the browser and type in "myFirstApp.dev" and my site would show up. Now I am getting an error in the browser that says "This site cannot be reached" (as shown in image1.jpg). How can I fix/diagnose the issue? Has anyone else ran in to this issue?
.
Found the answer to my own question. If anyone runs in to this same issue, here is an explanation. Google released Chrome v63 which forces all .dev domains to https. To fix this either enable SSL in Laragon or chance the domain extension your projects (.test for example). This will require changing your hosts and {Laragon Root}\etc\nginx\sites-enabled files.
https://forum.laragon.org/topic/761/chrome-63-now-forces-dev-domains-to-https/6
We built a passbook server on ASP.NET and it worked perfect in Dev. environment (without SSL certificate).
Passes that were generated could be seen on iPhone (in dev. mode) and on Mac.
Then we bought an SSL from Thawte (just for the domain) and added the certificate to IIS.
Of course, domain name is associated with the same IP address.
So now, when a link to the pass is generated on our server, normal iPhone can't download it, saying "Can't download the file".
If I click the same link in Safari on Mac, it is opened, when click it from Chrome - file is downloaded.
We've tried whatever was possible - enabling SSL 2.0, then SSL 3.0 on the server. We also trued disabling all SSL and enabling all TLS instead - no luck.
The aspnet passbook server is configured using the following.
SSL 2 (disabled)
SSL 3 (disabled)
TLS 1.0 (enabled)
TLS 1.1 (enabled)
TLS 1.2 (enabled)
here is the ssl test result: http://clip2net.com/s/3lUpIiq
seems pretty configured correctly.
the pass can be viewed/run to any mac safari browsers, downloads pretty well on non-safari browsers, but not on iphones.
it just says, cannot download the file. we have been trying to search the internet for possible answers but no luck.
the thing is that the browsers including mac safari recognizes well the certificate installed on the aspnet passbook server. but it seems iphones does not recognize the certificate.
Please advise what else could be done?
Thanks!
Does the webServiceUrl have 'https'? If not, it needs to (see https://developer.apple.com/library/ios/documentation/UserExperience/Reference/PassKit_Bundle/Chapters/TopLevel.html#//apple_ref/doc/uid/TP40012026-CH2-SW3).
Other than that, you should be able to view the error from Passbook in the console window in XCode.
We found out what the error was, when we tried to debug it on a MAC with XCode. What it showed was the pass was missing some required fields, in our case, the icon/logo image, and second was the pass registration endpoint had some errors.
We tried to fix these issues including our pass registration endpoint. After that, all went well and has been working smoothly.
Depending on the pass type, there must be required fields that must be met, else, the pass won't install correctly on production mode.
Many thanks!
I have an application that displays PDF files via Crystal Reports in a new window to the user. This works perfectly on my development machine and when accessing the site directly on the production server (remote desktop running browser installed on server) but when i access the site from the out side over the internet i get the error. Other reports display fine and this report used to work until i recently made some changes and re-installed the site. All code is in try ... catch but not info is being written to my error files. Cant figure out why it would work locally on the server but not over the internet and only this one report.
Have tried the System.Web attributes maxRequestLength and executionTimeout.
The Server is:
Windows Web Server 2008
IIS 7
Framework 4
This turned out to be an issue with the crystal report file, i never found out exactly why but i narrowed it down to one of the fields causing the problem, remove the field and no problem. I think it may have been linked to the reports xml based data source but cannot prove it.
Probably a firewall setting. Please make sure your firewall explicitly allows incoming connections to the TCP port 80 (or 443 for https, or anything else if you are accessing the site via another port) and try again.
I'm trying to enable SSL in IIS 7 on my dev machine using a self signed cert. This is turning out to be quite frustrating.
I have followed THIS guide and several others that are almost identical. The configuration goes ok, but when I try and navigate to the website I get various errors.
http://localhost/index.htm - Results in HTTP Error 404 - Not Found.
https://localhost/index.htm - Results in Internet Explorer cannot display the webpage.
If I go into IIS and remove the https binding from the website then it works as expected (in http only obviously).
I'm gussing that there is something that needs to be set up / configured / installed in windows before this will work?
Thanks.
You shouldn't need to reboot, it looks like IIS is not responding for some reason. Do you have Skype installed by any chance? It is unfortunately one of the most common reasons we see issues with ports.
So do this:
Open IIS Manager, and select the server
Click in the Sites page and make sure Default Web Site is Started.
If it is not running click Start
Also to troubleshoot in case it is a port issue:
OPen an elevated command prompt and type
netstat -ano
Search in there for something like 0.0.0.0:80 and :443
You will be able to see the Process ID (PID) that i using that port.
Also to troubleshoot SSL, you can run in the same command prompt "netsh http show sslcert" and you should see in there the certificate you assigned.