@jaredbusch said in Sodium: Session Timed sign out:

@quixoticjeremy said in Sodium: Session Timed sign out:

@gjacobse said in Sodium: Session Timed
sign out:

@Sodium has come a long way in the last few months. But currently with the 20 minute signout - it's not something I can really use. It's just really impractical for me to return from addressing a issue after 15 - 20 minutes and have to sign in again...

Duly noted. This was a security choice but as this is not the first time I've heard this we will be looking into changing this.

Don’t choose for me. Give me a remember me button that makes it last 24 hours at a minimum. Keep 20 minutes if you want for those that don’t check it.

This a Chrome-esque disaster. You can recommend all you want, but you cannot force me to do something. I will si ply not use you.

I think you're absolutely right. It all needs to simply be options to select from.

And there goes a successful mail test.

Mar 7 11:25:24 relay01 postfix/smtpd[2206]: connect from owncloud.domain.local[10.201.1.17] Mar 7 11:25:24 relay01 postfix/smtpd[2206]: CB2E6C0C82CB: client=owncloud.domain.local[10.201.1.17] Mar 7 11:25:24 relay01 postfix/cleanup[2208]: CB2E6C0C82CB: message-id=<[email protected]> Mar 7 11:25:24 relay01 postfix/qmgr[1665]: CB2E6C0C82CB: from=<[email protected]>, size=591, nrcpt=1 (queue active) Mar 7 11:25:24 relay01 postfix/smtpd[2206]: disconnect from owncloud.domain.local[10.201.1.17] Mar 7 11:25:26 relay01 postfix/smtp[2209]: CB2E6C0C82CB: to=<[email protected]>, relay=domain-com.mail.protection.outlook.com[216.32.181.170]:25, delay=2.1, delays=0.05/0/0.62/1.4, dsn=2.6.0, status=sent (250 2.6.0 <[email protected]> [InternalId=42704859829911, Hostname=SN1PR0201MB1854.namprd02.prod.outlook.com] 7564 bytes in 0.244, 30.254 KB/sec Queued mail for delivery) Mar 7 11:25:26 relay01 postfix/qmgr[1665]: CB2E6C0C82CB: removed

@Dashrender said in Unable to connect to RDP:

@JaredBusch said in Unable to connect to RDP:

@Dashrender said in Unable to connect to RDP:

@JaredBusch said in Unable to connect to RDP:

@Dashrender said in Unable to connect to RDP:

Does it work from a computer on the same network at the server?

Looking to see if it's an ZT problem or a Server problem.

Same error over normal IP also once I brought up my IPSEC tunnel

OK but you still haven't tried from another PC on that network - i.e. no VPN.

Does not matter. No one connect on network. Also two differnt IP protocols do not work. Issue is not whatever the hell you are driving at.

two different IP protocols? 😉

/sigh... IP subnets.

@FiyaFly said:

I have Centurylink at home. I can do a quick check from there when I get home. Maybe unrelated, but I was having some severe issues with DNS a couple weeks back at home.

I'll post more info on my findings tonight.

Thanks.