Server rentals :: NFOservers.com

Hmm. No reason that I can think of for it happening on this end, apart from what TimeX said. If I see it happen to me personally, I will be able to investigate further in depth.

Is your browser string or IP address changing? These could cause your token to no longer validate. If you're curious about the cookie lifetime, you should be able to check that through your browser's development tools. login_logout.pl should be fixed to work around your https issue now. That http re...

Sorry, I meant that the form didn't submit to a HTTP link. It submitted to HTTPS, and it was handled properly. The HTTP redirect that it responded with just that -- a simple redirection. When a client submits a HTTP request, our site automatically redirects to the HTTPS version, and that second redi...

The form wasn't submitted via HTTPS. That was just a redirect after the submission.

Either type of link is fine. http:// links don't need to be supported nowadays and there isn't really a reason to support them with the generic //.

It's certainly an interesting Firefox bug. Hard to say what triggered it, but if you have it on other pages, we can change those links, too.

It looks like it was redirecting to a http:// URL instead of https://. This shouldn't cause problems, because it would just redirect again upon the http:// page load, but you must have had a plugin or other configuration that interfered. Possibly an old and buggy https-everywhere type of plugin? (Th...

Yes, I tried that as well. No problems with it in Firefox 102.9.0esr, Chrome 111.0.5563.65, Edge 110.0.1587.69, or Safari on IOS 16.3.1. Correctly shows the error. Seems as though you may either have a plugin issue, identified a bug in your specific combination of browser and platform, or have a con...

Some applications may, but I wouldn't expect that to be widespread, since using the cookie method for CSRF is a cleaner and more maintainable way. That would be a fairly complicated attack vector (somehow forcing just the user's csrfcookie to be cleared, then have the user visit another link that se...

Having the CSRF token in a cookie is the standard way of handling it -- you may be thinking of a different type of token, such as a PHP session token. A CSRF token doesn't need to be stored server-side. With CSRF, the idea is that an attacker could trick a user into making a page submission, using G...

The login system was changed today in a way that may break unofficial automation utilities. Specifically, "cookietoken" was renamed to the more-apt "csrftoken". This will impact POSTs that submit with an email and password specified through a cookie (when an email and password ar...

I have not had much time to experiment with the beta beyond looking at its requirements and seeing that it is set up much differently than our current system, with a significantly larger footprint. I hope to find some more time in the coming weeks. Since TS3 also supports file transfers, I don't exp...

I'm sure we'll be seeing a lot start using ChatGPT, too, for more realistic-sounding content that can't be directly found elsewhere.

I have not heard of our IP ranges being blocked overall. I would recommend contacting them and asking if you are blocked, and why.

As a follow-up to this, the transition to PHP 8.1 was completed over the last month for all customers.

The primary user (current owner) can cancel the subscription through the Payments page in the control panel, after which the Panel access page for the server can be used to switch it over to a different primary account. Then, the new owner will be able to re-subscribe.