Fails to load sites with a self-signed certificate

[dahjelle]

Hi!

I'm trying to load a page served on my local machine, but I keep getting a setURL exception https://localhost:8443 message in the dev console, and a blank page with a loading indicator.

I wonder if this has something to do with having a self-signed certificate on that domain? I get similar behavior on other sites with self-signed certificates.

I'd be completely fine with manually importing certs or some such, but I don't know how to do that either.

Any thoughts?

[mark-hahn]

I'd be completely fine with manually importing certs or some such, but I
don't know how to do that either.

I think that you set it up in the desktop chrome browser and the atom one
will use the same settings. You should test it in the desktop browser
first. If something doesn't load on the desktop it won't load in Atom
either. Let me know if this helps.

In any case, there shouldn't be exceptions. Can you give me an example URL
so I can handle the error better?

On Tue, Mar 10, 2015 at 1:11 PM, David Alan Hjelle <notifications@github.com

wrote:

Hi!

I'm trying to load a page served on my local machine, but I keep getting a setURL
exception https://localhost:8443 message in the dev console, and a blank
page with a loading indicator.

I wonder if this has something to do with having a self-signed certificate
on that domain? I get similar behavior on other sites with self-signed
certificates.

I'd be completely fine with manually importing certs or some such, but I
don't know how to do that either.

Any thoughts?

—
Reply to this email directly or view it on GitHub
#42.

[mark-hahn]

Oh wait. Are you using a file:// protocol? There is a bug in the
webview tag that has been fixed but not landed in Atom yet. This may be
the cause of your problem.

On Tue, Mar 10, 2015 at 5:32 PM, Mark Hahn mark@hahnca.com wrote:

I'd be completely fine with manually importing certs or some such, but
I don't know how to do that either.

I think that you set it up in the desktop chrome browser and the atom one
will use the same settings. You should test it in the desktop browser
first. If something doesn't load on the desktop it won't load in Atom
either. Let me know if this helps.

In any case, there shouldn't be exceptions. Can you give me an example
URL so I can handle the error better?

On Tue, Mar 10, 2015 at 1:11 PM, David Alan Hjelle <
notifications@github.com> wrote:

Hi!

I'm trying to load a page served on my local machine, but I keep getting
a setURL exception https://localhost:8443 message in the dev console,
and a blank page with a loading indicator.

I wonder if this has something to do with having a self-signed
certificate on that domain? I get similar behavior on other sites with
self-signed certificates.

I'd be completely fine with manually importing certs or some such, but I
don't know how to do that either.

Any thoughts?

—
Reply to this email directly or view it on GitHub
#42.

[dahjelle]

Thanks! Yes, after I imported the certificate (Chrome on OS X uses the built-in Keychain.app for certificates, apparently) it loads fine. I should have thought of that earlier!

As far as the exception, you can see it by going to https://webmail.thehjellejar.com. This page has a certificate->URL mismatch that triggers a setURL exception https://webmail.thehjellejar.com exception.

[mark-hahn]

This web-browser package is no longer supported. Use the atom package browser-plus instead.