Sorry folks, some of you run again into the let's-encrypt certificate issue we had some month ago. I was stupid enough to try it again with let's-encrypt for the new url..
I just installed a new Certificate for the new tracker.gaytor.rent url
everybody should be able to connect now ! maybe you need a restart if not
hope that helps 
i just installed a new SSL certificate not issued by Let's Encrypt for our tracker. It should now work everything as expected..
also the forum issue with the lost connection problem is solved and should not happen anymore
enjoy
damn.. you just like sex...
get yourself a friend and try it real. if you have more real sex you will watch less porn
I would appreciate your feedback on today's design update. Some of you have already reported about fonts that are too small. It is always very important to know where exactly on which page you see a problem. Then we save ourselves unnecessary questions back and forth. Of course I am also happy about every positive feedback, without any change wishes. :cheers:
@ianfontinell said in I have a serious concern regarding to the old gt domain:
I know we're moving, but I haven't heard any technicality as to if you'll still own this one and for how long, or if people will be greeted by any warning when visiting gt.ru - so my concern is that the domain might be used to phish user accounts as this could seriously damage the community.
At least for the next 10
Years
Is that enough ?
does this happen to the gaytor.rent site or the .ru site?
i just made some changes to the configuration.. hope this is fixed now.. sorry for the delay
@looselips said in 413 - Request Entity Too Large:
@DandyLion said in 413 - Request Entity Too Large:
@john32123666 Thank you for pointing this out,
I have sent a message over to our SysAdmin to try and sort this out. It appears the system is not resizing the files which is causing the "Too large" error message.
DandyLion
Thanks I thought I was the only one having this issue lol. Please let me know when it's resolved
@realstik we are working on a solution... in case of a .ru tld ban... it is not easy task due to all the torrents out with encoded .ru urls inside your torrents.
Because of family matters I could not take care of the errors on the new site before.
The error described above should be fixed now. Also the upload of pictures in usual file sizes should work as expected.
Due to a small misconfiguration after I "finished" the new site, a logfile filled up and took all the memory on the disk.
There were also a few other small bugs fixed without knowing what effect they had on the site.
If anything does not work, please test the same link on the .ru page. If it works there, I am grateful for any detailed error report. Please ALWAYS send urls where the error happens. Thanks !
@cocadao said in New Forum Software:
I'll be happy to participate and test it out. lol
this is SO AWESOME !
@ianfontinell said in Will QTM still work after the domain change is complete?:
I was wondering if there will be any issue or if it'll work as always without user interference or a new build of the QTM since it's pretty much unmodified since 2018.
step by step...
@ianfontinell thanks for reporting. This should be fixed by now. Appreciate your intense testing.
cheers
As you might already read on our homepage:
The search in our torrent lists had not been very accurate lately. Today we have installed an update which allows more accurate searching.
Previously, search terms like > "blow job" anal -twink
were not very well supported and returned way too many results. In worst case and with more complicated search terms the script even crashed.
if you find still any buggy result, let me know
hopefully you like this change
more information from letsencrypt can be found here: https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/
@pajac99 checkout Trulicity
this was a huge gamechanger for me
it can also used if you do not have diabetes.. they sell the exact same with a different name
i would not say "no" if you supply a new set of category images...
one thing: could you also supply a .psd file? so i can create new ones with the same style myself...
@bc22 @raphjd
since nobody supplied a fix, i change the colors on my own.. should be readable by now...
just to let you know how this specific change look like:
.chat-list {
border:none;
border-left:none;
border-right:none;
border-bottom:none;
}
.quick-search-container .quick-search-results li a {
color: #ffffff;
}
.header .chat-list, .slideout-menu .chat-list {
color: #ffffff;
}
.header .chat-list>li:not(:last-child), .slideout-menu .chat-list>li:not(:last-child) {
border-bottom:none;
}
.chats-list>li {
border-left: none;
border-right: none;
}
hey folks,
this bug is caused due to some UTF-8 encoding problems which should be fixed by now
if you still experience errors, you could check if the rss is valid by using your url here:
https://validator.w3.org/feed/
if you see any errors, please report the link which generates the faulty result but do not include your passkey 