Improvements to logging / failure during nzb addition

[DarrenPIngram]

• What do you want to happen? It would be nice if the application could have an action button that would save out the log for the last executed command/instruction so it could be communicated to support (rather than the current arrangement).

Reason is I use the application HEAVILY but at times you get "unknown error"-type messages, particularly (but not exclusively) when connecting over the wifi using my iPad (it also happens on a desktop).

This way straight away the captured session could be exported and reported.

• If not clear, why do you want it?
• Do you think it's something only you need or something that might be popular? Hopefully it would not be popular, since errors should be small, but it could help track down insidious issues for the good of everyone.

Bonus if the report could be automatically sent from the pop-up error button on command (or automatically if set in preferences).

• If not clear, explain the use case.

[DarrenPIngram]

Example of a helpful error:

https://i.postimg.cc/BZzqrrqh/Screenshot-2022-08-13-at-17-06-47.png

[DarrenPIngram]

Unsure if related but no pop-up mentions this.

2022-08-13 05:08:50.930 WARN --- [http-nio-127.0.0.1] o.n.auth.AuthAndAccessEventHandler : [ID: 57526, Host: xxxxx] Access denied to IP xxxxx: Invalid CSRF Token 'null' was found on the request parameter '_csrf' or header 'X-XSRF-TOKEN'.

2022-08-13 05:08:50.931 WARN --- [http-nio-127.0.0.1] o.n.auth.LoginAndAccessAttemptService : [ID: 57526, Host: xxxxx] 1859 failed access attempts from IP/host xxxxx in the last 24 hours. Will block access after 5 failed attempts

Running NZBHydra on a remote server, accessing from home, XXXXX is my home IP and reverse DNS lookup.

[theotherp]

Would be helpful to find the cause of the error. Showing proper error message depends on that.

[DarrenPIngram]

A bit difficult and debug logging is not viable with the amount of traffic being handled. If the app itself kept x minutes of debug log and could be fired immediately with a "now an error has occurred" button it may help.

It does not happen so often, but seems to come in waves, so I've not detected a pattern yet.