Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rustls https errors on atomicdata.dev #240

Closed
joepio opened this issue Dec 11, 2021 · 10 comments · Fixed by #245
Closed

rustls https errors on atomicdata.dev #240

joepio opened this issue Dec 11, 2021 · 10 comments · Fixed by #245
Labels
bug Something isn't working

Comments

@joepio
Copy link
Member

joepio commented Dec 11, 2021

The server keeps going down since running 29.2, and it throws these errors:

[2021-12-11T23:44:04Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-11T23:44:04Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-11T23:44:04Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-11T23:44:04Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }

@joepio joepio added the bug Something isn't working label Dec 11, 2021
@joepio
Copy link
Member Author

joepio commented Dec 11, 2021

Tried removeing the https folder from config, since a few restarts did not help.

After that, the server got stuck on [2021-12-11T23:49:07Z WARN atomic_server::https] HTTPS TLS Cert init sucesful! Stopping HTTP server, starting HTTPS...

@joepio
Copy link
Member Author

joepio commented Dec 12, 2021

I think the problem was that the HTTP port was not set, so defaulted to the new 9883 value, instead of 80.

@joepio joepio closed this as completed Dec 12, 2021
@joepio
Copy link
Member Author

joepio commented Dec 12, 2021

Hmm it went down again... Not sure if it was the HTTPS error, though, forgot to save logs

@joepio
Copy link
Member Author

joepio commented Dec 12, 2021

Yes, it's that same issue.

[2021-12-12T11:30:13Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-12T11:30:13Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-12T11:30:13Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-12T11:30:13Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-12T11:30:15Z WARN  rustls::conn] Sending fatal alert HandshakeFailure
[2021-12-12T11:30:15Z WARN  rustls::conn] Sending fatal alert NoApplicationProtocol
[2021-12-12T11:30:15Z WARN  rustls::conn] Sending fatal alert ProtocolVersion
[2021-12-12T11:30:15Z WARN  rustls::conn] Sending fatal alert HandshakeFailure
[2021-12-12T11:30:27Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-12T11:30:27Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-12T11:30:27Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-12T11:30:27Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-12T11:30:45Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-12T11:30:49Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-12T11:30:53Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }
[2021-12-12T11:30:56Z ERROR rustls::conn] TLS alert received: AlertMessagePayload {
        level: Fatal,
        description: BadCertificate,
    }

@joepio
Copy link
Member Author

joepio commented Dec 12, 2021

actix/actix-web#2507

@joepio
Copy link
Member Author

joepio commented Dec 12, 2021

I'm seriously considering rolling back actix-web to v3.x. Will break Tauri builds, but that's a nice to have anyway. I think I've learned my lesson on upgrading too early to beta software :)

Should also fix #283

joepio added a commit that referenced this issue Dec 12, 2021
joepio added a commit that referenced this issue Dec 12, 2021
joepio added a commit that referenced this issue Dec 12, 2021
joepio referenced this issue Dec 19, 2021
Upgrade actix version, it compliles

#215 WIP actix running in tauri!

#215 Fix actix routing

Improve tauri docs

Fix migration
@joepio
Copy link
Member Author

joepio commented Dec 21, 2021

Just noticed this on atomicdata.dev, after the server went down without a specific panic log

[2021-12-21T04:36:19Z WARN  rustls::server::tls13] Resumption ignored, DHE_KE not offered

@joepio
Copy link
Member Author

joepio commented Dec 29, 2021

This comment is interesting:

6bb7412#r62189445

joepio added a commit that referenced this issue Dec 30, 2021
joepio added a commit that referenced this issue Dec 30, 2021
@joepio
Copy link
Member Author

joepio commented Dec 30, 2021

This fixes it, had nothing to do with actix:
77bbfb4

joepio added a commit that referenced this issue Dec 30, 2021
* #246 update actix again

* #240 fix rustls

* #246 fix server test

* #246 publish tauri action

* #246 changelog
@joepio
Copy link
Member Author

joepio commented Dec 30, 2021

It's still here...

2021-12-30T13:43:13.838283Z  WARN rustls::conn: Sending fatal alert HandshakeFailure
2021-12-30T13:43:59.125224Z  WARN rustls::conn: Sending fatal alert HandshakeFailure
2021-12-30T13:44:42.298872Z  WARN rustls::msgs::handshake: Illegal SNI hostname received [49, 48, 56, 46, 54, 49, 46, 50, 53, 50, 46, 53, 48]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant