R+
R+
Hi, So the Preset workflow/connectflow goes like this: the admin setup the Preset items, and the items are sent to clients as is to be displayed on the "Presets" list....
Presets can only be specified by the server admin. But once the user used a Preset, there will be an item added to the "Connected before" list. The "Connected before"...
I don't really have energy left to review PRs. Can you make a separate fork to add the change? I'll add a link here (to the `README.md` file) to redirect...
I would still recommend that you do a separate fork. Reasons: 1. I have other plans for Presets, namely, it will be completely server-side with no data downloaded to the...
Try run Sshwifty with environment variable `SSHWIFTY_DEBUG` set to 1. $ SSHWIFTY_CONFIG=./sshwifty.conf.json SSHWIFTY_DEBUG=1 ./sshwifty This enables Sshwifty to print more detailed logs, including every request it received on the server...
Hi @ech0corday, not really sure what's happened based on the log. But I feel the `5m1.676125988s` runtime (the time Sshwifty backend spent on the request) is interesting since it's almost...
@ech0corday You can set environment variable `SSHWIFTY_DEBUG` to anything but empty to enable more detailed logs. But it's mainly helpful for indicating internal procedures, I don't think it'll provide much...
@ech0corday I don't really believe screen v.s. systemd would be the cause, assuming everything else is configured the same. The log `Close 1006 (abnormal closure): unexpected EOF` indicates that the...
Odd. In my theory, a longer timeout should actually make this problem worse. Maybe I guessed it wrong. I need to check something up on my end to dig this...
Update: My theory above was indeed wrong. Sshwifty will work fine under Firefox, but under Chrome, the browser slows down all timers created under a tab if the tab is...