Howdy all,
Is the sysop login in webv4 disabled? If I login with my sysop account, it doesn't say the login is incorrect, but it doesn't log me in. It just seems to refresh the page.
Works fine with regular user accounts, but I'm a little mystified with this one currently.
Is the sysop login in webv4 disabled? If I login with my sysop account, it doesn't say the login is incorrect, but it doesn't log me in. It just seems to refresh the page.
Works fine with regular user accounts, but I'm a little mystified with this one currently.
Is the sysop login in webv4 disabled? If I login with my sysop account, it doesn't say the login is incorrect, but it doesn't
log me in. It just seems to refresh the page.
Works fine with regular user accounts, but I'm a little mystified with this one currently.
Works for me on Vertrauen. What is the name/alias of your sysop account?
Are you using the Sysop password, or your regular password? Webv4 uses your regular password until it needs to use fTelnet to
do something and then fTelnet prompts for the SYS password...
Re: Webv4 sysop login?
By: Digital Man to Trikester on Mon Jan 03 2022 11:21 pm
Is the sysop login in webv4 disabled? If I login with my sysop account it doesn't say the login is incorrect, but it doesn't log me in. It ju seems to refresh the page.
Works fine with regular user accounts, but I'm a little mystified with this one currently.
Works for me on Vertrauen. What is the name/alias of your sysop account?
This one, Trikester. One thought I had on it was - if the system password is required elsewhere, is it not required in the web login?
This one, Trikester. One thought I had on it was - if the system password is required elsewhere, is it not required in the web login?
Just your sysop alias and password (not the system password) should work.
Are you able to log in using some other account, even a non-sysop one?
Are you able to log in using some other account, even a non-sysop one?I'm able to login with a non-sysop account, yes.
ProxyPreserveHost On
seems to be pretty critical when using webv4. With that in, the cookie issue (invalid domain) went away.
There's still an error in the browser console complaining about the synchronet cookie will soon be rejected because it has the "SameSite" attribute set to "None" or an invalid value, without the "secure" attribute.
ProxyPreserveHost OnGlad to hear it's working. I don't think webv4 is doing anything unusual, so this would probably be a problem for many upstream
seems to be pretty critical when using webv4. With that in, the cookie issue (invalid domain) went away.
servers that use cookies.
There's still an error in the browser console complaining about the synchronet cookie will soon be rejected because it hasThanks for the heads up. Should hopefully be a simple fix when I get to it.
the
"SameSite" attribute set to "None" or an invalid value, without the "secure" attribute.
What browser was this?
No worries - I figured most of it was due to just not having tested this with apache's reverse proxy enough initially. I think this is one item that doesn't have much said about it in the Synchro wiki - no config example that I noticed, anyway.
ProxyPreserveHost OnGlad to hear it's working. I don't think webv4 is doing anything unusual, so this would probably be a problem for many upstream
seems to be pretty critical when using webv4. With that in, the cookie issue (invalid domain) went away.
servers that use cookies.
There's still an error in the browser console complaining about the synchronet cookie will soon be rejected because it hasThanks for the heads up. Should hopefully be a simple fix when I get to it.
the
"SameSite" attribute set to "None" or an invalid value, without the "secure" attribute.
No worries - I figured most of it was due to just not having tested this with apache's reverse proxy enough initially. I think this is one item that doesn't have much said about it in the Synchro wiki - no config example that I noticed, anyway.
If I get around to replacing this Apache install with nginx I'll have to see what the equivalent configs are like.
I have it running behind a nginx proxy and I'm going to post my config to the Wiki when I get a chance. It is fairly standard settings, but WebV4 definately doesn't work if you try to do just do a proxy pass without all of the other parameters.
It'd be good to have some generalized documentation up there about
using HTTP reverse proxies, and let the sysop adapt them to whatever
package they're using. IMHO they should learn how to configure
whatever third party software they chose, and we can't cover the whole
gamut of available proxy packages - but the same concepts will always
apply.
The most common omission / point of confusion is configuring proxying
to the websocket service, but a few other tweaks are probably needed
most of the time.
That'll be great, look forward to seeing that.
Re: Webv4 sysop login?
By: Xerxes to Trikester on Tue Jan 04 2022 09:32 am
> Are you using the Sysop password, or your regular password? Webv4 uses your regular password until it needs to use fTelnet to
> do something and then fTelnet prompts for the SYS password...
Yup, just the account's regular password - even tried an FTP login userpassword:syspassword style without success.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 295 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 02:34:18 |
| Calls: | 6,642 |
| Calls today: | 2 |
| Files: | 12,190 |
| Messages: | 5,325,502 |