Tutanota: Appimage not working, can't access web mail

[personaaleatoria]

• [x] This is not a feature request (existing functionality does not work, not missing functionality).
  I will request features on forum or via support.
• [x] I've searched and did not find a similar issue.

Describe the bug
I can't log in my email account using the appimage.

To Reproduce
Steps to reproduce the behavior:

1. execute appImage
2. input the email credentials
3. hangs forever
4. see connection error in console

Expected behavior
I can log in to the email

Console output:

./tutanota-desktop-linux.AppImage
Icon theme "Numix-Circle-Light" not found.
[2020-08-15T15:52:50.350Z] the monkey has been patched
[2020-08-15T15:52:50.417Z] config up to date
[2020-08-15T15:52:50.473Z] version:   3.76.6
[2020-08-15T15:52:50.955Z] alarm storage initialized
[2020-08-15T15:52:51.004Z] scheduling to reconnect sse in 1 seconds
[2020-08-15T15:52:51.006Z] startFile:  file:///tmp/.mount_tutanoTOmb7C/resources/app.asar/desktop.html
[2020-08-15T15:52:51.408Z] default mailto handler: false
[2020-08-15T15:52:52.008Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:52:52.008Z] sse info not available, skip reconnect
[2020-08-15T15:52:53.556Z] Webapp ready
[2020-08-15T15:52:53.558Z] autoUpdater info:
 checking-for-update
[2020-08-15T15:52:53.641Z] /home/user/.local/share/applications/tutanota-desktop.desktop does not exist, checking for permission to ask for permission...
[2020-08-15T15:53:02.011Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:53:02.012Z] sse info not available, skip reconnect
[2020-08-15T15:53:12.020Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:53:12.020Z] sse info not available, skip reconnect
[2020-08-15T15:53:22.025Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:53:22.025Z] sse info not available, skip reconnect
[2020-08-15T15:53:32.033Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:53:32.033Z] sse info not available, skip reconnect
[2020-08-15T15:53:42.040Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:53:42.040Z] sse info not available, skip reconnect
[2020-08-15T15:53:52.041Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:53:52.041Z] sse info not available, skip reconnect
[2020-08-15T15:54:02.048Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:54:02.048Z] sse info not available, skip reconnect
[2020-08-15T15:54:12.056Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:54:12.056Z] sse info not available, skip reconnect
[2020-08-15T15:54:22.064Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:54:22.064Z] sse info not available, skip reconnect
[2020-08-15T15:54:32.071Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:54:32.071Z] sse info not available, skip reconnect
[2020-08-15T15:54:42.082Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:54:42.082Z] sse info not available, skip reconnect
[2020-08-15T15:54:52.083Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:54:52.083Z] sse info not available, skip reconnect
[2020-08-15T15:55:02.092Z] scheduling to reconnect sse in 10 seconds
[2020-08-15T15:55:02.093Z] sse info not available, skip reconnect
[2020-08-15T15:55:03.807Z] autoUpdater error:
 Auto Update Error 1, continuing polling:
net::ERR_PROXY_CONNECTION_FAILED
[2020-08-15T15:55:03.807Z] autoUpdater error:
 Update check failed, net::ERR_PROXY_CONNECTION_FAILED
[2020-08-15T15:55:12.100Z] scheduling to reconnect sse in 10 seconds

Web mail is also not working

[personaaleatoria]

multiple checks

[esotericDisciple]

Android app is also not working

[heyheyhello]

tutanota.de is also down, likely because it redirects to the .com

[AFulgens]

A couple weeks ago there was a TLS Error (PR_END_OF_FILE_ERROR), now this. Are these general stability issues, or sporadic without underlying cause and it just happened that the errors were within 1 month of each other?

[bkmo]

Mail done right..........

[mj-saunders]

@AFulgens I wondered what that was. This seems a little worse.
This thread is looking like it's becoming the place to discuss the issue.
Does anyone have an idea as to what's happened this time?
Is this our only portal to the tutanota team?

@bkmo I assume you mean "down" - and yes, it is...

[Usodiariom]

The website in general is down, both .com and .de, we must wait.

https://mastodon.social/@Tutanota/with_replies

https://twitter.com/TutanotaTeam/status/1294655776167002112

We are currently facing a downtime. We are actively working on this. Sorry for any inconvenience!

https://en.wikipedia.org/wiki/Tutanota

[Usodiariom]

A couple weeks ago there was a TLS Error (PR_END_OF_FILE_ERROR), now this. Are these general stability issues, or sporadic without underlying cause and it just happened that the errors were within 1 month of each other?

In these last weeks GNU / Linux suffered important changes in the updates, it may have to do with this

It's a bit weird that they don't have enough support to test before updating.

[mj-saunders]

@Usodiariom thanks a lot. I didn't think to check their mastodon. Much appreciated.

[bkmo]

It's not down......looks like I'M offline

"Could not reach server, looks like you are offline. Please try again later."

[mj-saunders]

@bkmo ...it's not just you

The website in general is down, both .com and .de, we must wait.

https://mastodon.social/@Tutanota/with_replies

https://twitter.com/TutanotaTeam/status/1294655776167002112

We are currently facing a downtime. We are actively working on this. Sorry for any inconvenience!

https://en.wikipedia.org/wiki/Tutanota

[bkmo]

Sorry....that was my attempt at sarcastic humor.

[AFulgens]

Huh, curl could query the site and received the correct and full HTML. Although only after minutes, thus it's reasonable that all meaningful browsers are timing out. This also means that the servers are up and running, and the reassurance they gave on Twitter about the received e-mails not bouncing but they'll be delivered after the servers are up again, totally reasonable and expected.

We should just wait and stop pinging the site I guess until they figure out the problem :) Although, it would be interesting to know, what causes such outages. Maybe a public post mortem post later on?

[AFulgens]

According to their Twitter it was a sustained DoS attack, which seems consistent with my last comment.

[personaaleatoria]

it works now

[AFulgens]

In case somebody is not monitoring social channels, but is reading this thread: https://tutanota.com/blog/posts/update-ddos-attack/

[mj-saunders]

@AFulgens brilliant - thank you