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!
Related
Doing dev work on several sites on my local (Windows 10) PC when out of the blue this morning one site refuses to load in Microsoft Edge (Version 89.0.774.45 (Official build) (64-bit)). Other local sites are working fine.
I removed the redirect to SSL from web.config and issued a fresh self-signed certificate: NET::ERR_CERT_COMMON_NAME_INVALID - You can't visit local-prodject.mydomain.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.
There is no HSTS in web.config. I removed the HTTPS redirect from web.config and it's still trying to force HTTPS. I've done the edge://net-internals/#hsts to delete for local-prodject.mydomain.com and localhost, no change.
I'd prefer to have self-signed working as it was yesterday, and on other sites on my local PC so when they get pushed to a production environment they're ready to go.
I should also note that Chrome and Firefox (Dev and regular) work fine.
Chrome, Opera and Edge have a safe word you can use to bypass this SSL issue for local development. Click anywhere within the browser window and type: thisisunsafe
I have hosted a web service Windows 2019 IIS 10.0.
Created a self-signed certificate and created the binding.
But I am getting the address mismatch error also when I am trying to open the link using chrome (on the server) it is not opening.
Please help.
enter image description here
Error in IE:Error Code: DLG_FLAGS_SEC_CERT_CN_INVALID
But it is still opening with a certificate error.
Error in Chrome: ERR_CONNECTION_RESET
Make sure your hostname is in one of those fields - not in the friendly name, which doesn't play a part.
IE has more permissive certificate handling than Chrome. I had a misconfigured certificate where the hostname wasn't in the subject or SANs and got the same errors.
Last week I was able to build and run a locally-hosted .NET website without any problems. However, for the past couple of days I haven't been able to get around this error:
ERR_CERT_COMMON_NAME_INVALID
This error message appears in both Chrome and Firefox. Edge and IE will load the page but block all AJAX requests without explanation.
The website is configured as an application in IIS and uses a self-signed certificate (created in IIS).
I encounter the same problem with running a completely separate .NET website so I doubt it has anything to do with each website's individual configurations.
My colleagues are able to browse their locally-hosted versions of the same website using a self-signed certificate in the same browser versions as I have installed.
Please, can someone tell me what might have happened to my setup, why are browsers no longer accepting my certificate, and how to get back to a running localhost website?
I'm a PHP developer and to be able to work on my development environment with a certificate, I was able to do the same by finding the real SSL HTTPS/HTTP Certificate and deleting it.
The steps are :
In the address bar, type "chrome://net-internals/#hsts".
Type the domain name in the text field below "Delete domain".
Click the "Delete" button.
Type the domain name in the text field below "Query domain".
Click the "Query" button.
Your response should be "Not found".
You can find more information at : http://classically.me/blogs/how-clear-hsts-settings-major-browsers
Although this solution is not the best, Chrome currently does not have any good solution for the moment. I have escalated this situation with their support team to help improve user/developer experience.
You should redo these steps every time you go on the server that contains the main HTTPS Certificate with HSTS clause.
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. =]
I'm trying to connect to AMFPHP over SSL (self-signed) from a Flex 4.5 application.
Will this work? Or do I need an authority-signed certificate?
Will it silently fail or prompt user like it does in browser?
How do I need to edit the services-config.xml file for this to work?
Thank you.
I've done this before, and it works fine The one thing I'd suggest is that you make your page that houses the SWF on the same domain/cert, then the browser will prompt the user to accept the certificate before they even see the SWF. Once the cert is manually accepted, the AMFPHP stuff works fine. The default services-config should work fine but you can edit it to accept ONLY ssl connections for more security. The only IE issue I can remember off the top of my head is that there's a checkbox if your server sends the wrong caching header (no-cache) I think, IE will simply show a redx. This is resolved by changing a checkbox in IE.
I've never tried doing the client page on HTTP and the services on HTTPS but I imagine you might run into more issues that way.