Document "A fatal alert message was received from peer ..."

[warpok]

And how do I fix it?

• Reproduce the issue.
• Log the IP address.
• Check what to log more.
• Test it well.
• ChangeLog.

[teusbenschop]

This has been seen before.

It's discussed and/or mentioned in:

#899

#293

[warpok]

In 899, it appears that the issue is certificates. But before you wrote, I already tested to see if renewing certificates would solve the problem. The certs are good until December 22. Also, you will note that https is working, as seen in the screenshot above. I also upgraded the server before I wrote, so everything is using the newest version.

293 seems to be a different issue, having to do with Android version.

I admit that I didn't read the two threads in detail. Please let me know if you were referencing something different.

But guess what?! Suddenly now, a full hour after doing the above operations, the constant error has stopped.

How can I remove all traces of Google Cloud?
Journal message: Google access token: sh: 1: gcloud: not found

[teusbenschop]

If the fatal alert message is not caused as described in the issues mentioned above, then another option is that it is caused by a rogue device probing your website. It would help if the message about the "fatal alert" would also show the IP address that causes this alert.

About disabling Google Translate, it will be the inverse of enabling it, see the Settings/System menu, and see issue #803.

[warpok]

I had done the inverse of installing and enabling it already. But in the Settings > Recources area, I had not deleted the defined exports. I need to check if that message appears again.

I like your idea:

If the fatal alert message is not caused as described in the issues mentioned above, then another option is that it is caused by a rogue device probing your website. It would help if the message about the "fatal alert" would also show the IP address that causes this alert.

The reason that I like it is because of security concerns we have encountered in the past.

[teusbenschop]

The issue was fixed.

Due to bug #935 it always logs remote IP address 0.0.0.0. Once that bug is fixed, it will automatically begin to log the correct IP address.

Because of the low priority of this, there's no Ubuntu packages created for this.

[warpok]

Thanks!