# Change the auto logoff time **URL:** \ **Category:** General Inquries\ **Created:** [October 28, 2021, 11:41pm UTC](https://forums.interworx.com/t/change-the-auto-logoff-time/22361 "2021-10-28T23:41:47Z")\ **Posts on this page:** 3\ **Page:** 2
**Author:** ![sysnop](https://forums.interworx.com/letter_avatar_proxy/v4/letter/s/cdc98d/32.png) [@sysnop](https://forums.interworx.com/u/sysnop)\ **Post date:** [January 21, 2025, 9:10pm UTC](https://forums.interworx.com/t/change-the-auto-logoff-time/22361/21 "2025-01-21T21:10:32Z")
> [@IWorx-Jenna](#): > > Can you provide a bit more information regarding “But when doing it this way browsers are served the wrong certificate from a Siteworx domain on the same shared IP.” I’ll try to break it down… Server cert **method 1** - No Siteworx account for the server hostname, DNS zone only (dropdown selector/Let’s Encrypt): `https://server.hostname.com` - browser warning / SSL\_ERROR\_BAD\_CERT\_DOMAIN - certificate served is for a Siteworx domain with a certificate `https://server.hostname.com:2443/nodeworx` (or `/siteworx`) - all good Server cert **method 2** - Siteworx account for server hostname, its LE cert is used for the server hostname (dropdown selector/Domain): `https://server.hostname.com` `https://server.hostname.com:2443/nodeworx` (and presumably `/siteworx`) - both are good Siteworx domains have LE certs and no issues with webmail. In fact, `https://siteworxdomain.com/webmail` is enough (`:2443` isn’t needed). Thanks for the Apache snippet, I’ll use it. ---
**Author:** ![IWorx-Jenna](https://forums.interworx.com/user_avatar/forums.interworx.com/iworx-jenna/32/41_2.png) [@IWorx-Jenna](https://forums.interworx.com/u/IWorx-Jenna)\ **Post date:** [January 22, 2025, 1:57am UTC](https://forums.interworx.com/t/change-the-auto-logoff-time/22361/22 "2025-01-22T01:57:37Z")
Hello– Oh, okay, that is totally expected. Method 1: All you did was point DNS for the hostname to the server. The hostname does not have a corresponding vhost or index file. You pointed the domain, but there isn’t actually a _website_. The SSL created under Server\> SSL certificates for the hostname ONLY covers port **2443.** --it is creating a SSL cert for the **Internal Apache instance** to use for the hostname. When you access [https://hostname.com](https://hostname.com), you are accessing the hostname over port **443** , using the **system-level Apache version**. So Apache sees the request for [hostname.com](http://hostname.com) over 443 on IP address 123.45.67. Apache looks for a vhost matching [hostname.com](http://hostname.com) over 443 on IP address 123.45.67. It doesn’t see one. But it knows you want _something_ from the server over 443 for that IP address, so it looks at the first vhost, alphabetically, on the server, that has a 443 section, and serves that, instead. It’s basically this, but with the hostname instead of another SiteWorx account: [Wrong Website Showing Over HTTPS — InterWorx documentation](https://appendix.interworx.com/current/troubleshooting/domains_websites/ssl-on-shared-ip.html) If there weren’t any SiteWorx accounts on the server, or there were no vhosts with a 443 section for 123.45.67, Apache would then look at /var/www/html for an index file to serve. If it didn’t see anything there, it would give a 403, or serve the generic Alma or Rocky Linux welcome page, however your server is set up. (this: [403 Forbidden Error or OS-Specific Apache Page Showing Over HTTPS — InterWorx documentation](https://appendix.interworx.com/current/troubleshooting/domains_websites/forbidden-error-over-https.html)) When you specify using port 2443 for [hostname.com](http://hostname.com) in the url, that shows as all good because port 2443 is the internal Apache instance for InterWorx. That has an SSL cert that covers it for the hostname. Method 2: Since the hostname was created as a SiteWorx account, it DOES have a corresponding vhost, as well as an index file. It is both a domain that is pointed to the server AND a website. And, since you created its SSL cert in SiteWorx, the vhost also has a 443 section. So when you go to [https://hostname.com](https://hostname.com), the server-level Apache instance looks for a vhost matching [hostname.com](http://hostname.com) over 123.45.76 with a 443 section. It sees this, so it serves [hostname.com](http://hostname.com) over 443 with the corresponding SSL cert, using the index file in the homedir of the SiteWorx account. Since you then applied the domain-level SSL cert to the system services, that same SSL cert ALSO now covers port 2443. So when you access [hostname.com:2443](http://hostname.com:2443), the internal Apache instance can also see it. So the difference really all just comes down to, do you want [hostname.com](http://hostname.com) to be a website, with a vhost and index file, OR do you want [hostname.com](http://hostname.com) to just be a domain that resolves to the server. Hopefully that explaination makes sense. Let me know if it doesn’t–SNI is weird, lol. 🙂 re Webmail, that has its own proxy set up, so that it basically automatically does the redirect from [siteworxdomain.com/webmail](http://siteworxdomain.com/webmail) to [hostname.com:2443/webmail](http://hostname.com:2443/webmail), just a different way. Thanks, -Jenna ---
**Author:** ![sysnop](https://forums.interworx.com/letter_avatar_proxy/v4/letter/s/cdc98d/32.png) [@sysnop](https://forums.interworx.com/u/sysnop)\ **Post date:** [January 22, 2025, 2:26pm UTC](https://forums.interworx.com/t/change-the-auto-logoff-time/22361/23 "2025-01-22T14:26:15Z")
> [@IWorx-Jenna](#): > > Hopefully that explaination makes sense. Yes, it makes sense and I think I’m on track now. I really appreciate your taking the time to explain things so thoroughly. At one point it did occur to me the server hostname isn’t a web server and thought to myself, ‘Why would http, let alone https, be needed in the first place?’. I guess it was the working :2443/nodeworx throwing me off, and not taking into account Interworx runs on its own Apache instance. I knew much of this stuff, I’m just really out of practice. Not to mention the option of turning server hostname into a web server, which is how I always did it before, and my older expectations probably weren’t helping. Thanks again! [Previous page](https://forums.interworx.com/t/change-the-auto-logoff-time/22361.md?page=1)