Site Update: Things have changed, but nothing is final.

[fishburger67]

8 hours ago, Asrienda said:

Still getting issues, this is from today on Edge 103.0.1264.71 (Official build) (64-bit). 

GET RID OF THE HTTPS:// PART AND IT WILL WORK

[Mister X]

57 minutes ago, fishburger67 said:

GET RID OF THE HTTPS:// PART AND IT WILL WORK

 

No idea why to scream a wrong suggestion?

Spoiler

 

[LongDukDong]

Websites have converted from HTTP (HyperText Transfer Protocol) addresses over to HTTPS (HyperText Transfer Protocol Secure) as it increases websites safety and security.  Knowing that the site now uses this protocol to make LoversLab more secure, the removal of HTTPS is likely never going to happen.

 

I will acquiesce and say that typing "LoversLab.com" into a browser's URL window (Edge/Firefox) will bring up the windows thus stated by Fishburger67,  Do note that one of the windows states an error code of 1S160/2... whatever that may be. I too received the same error code as he using this means. Oddly, since I bookmarked LoversLab with an open-source third-party browser (neither of these) which I use a lot, I redirect straight and fine. But as I said, I bookmarked and have a 'history' using LL with this browser.

 

Note:  After repeat entry of LoversLab.com into Edge (also version 03.0.1264.71 64-bit)), I eventually did NOT go to the 1S160/2 error "Does Not Exist" page, likely entering into history.

 

Still, if one browses for Lovers Lab, merely by typing "LoversLab" alone (no .com attached), it would come up straight in a google search.  Bookmarking should pose no difficulty.

Edited July 25, 2022 by LongDukDong

[myuhinny]

On 6/25/2022 at 10:40 AM, Latuda said:

I have notifications of  reviews of  animators . How do I not get notified for this ?

 

I have no clue on that sorry.

[fishburger67]

13 hours ago, Mister X said:

 

No idea why to scream a wrong suggestion?

  Reveal hidden contents

 

Not screaming, just forgot to turn off caps lock.  Just suggesting to remove the https (or http) from in front of loverslab.com.  https://loverslab.com is a complete url.  loverslab.com is not and your browser will fix up the latter to work.   Note that the www part of a url references a particular server in the loverslab.com domain.  If it is not there, www is assumed, but it would easily be www1 or server1 as in http://server1.loverslab.com.  By convention only, www is the most common machine name in most domains.

[LongDukDong]

Understand a little about Web history.

 

It used to be that you could use FTP as a protocol to access websites, but it was a heavy-weight statement protocol and assumes you would be on the same server for quite some time...  optimized for large-scaled files.  Fine for uploading/downloading files for a site administrator managing large databases, but not for much else.  I've used it in the past... klunky.

 

HTTP came along and replaced it as a light-weight protocol to allow one to navigate multiple files, perfect for browsing the web and much easier to use than FTP. And it was designed around HTML code.  HTTPS now exists and  is just the latest upgrade to the protocols used to navigate the web.   Older websites that haven't upgraded will use HTTP, but newer ones will use HTTPS. as it is a more secure protocol.

 

https://NexusMods.com is not a complete URL .  However, entering it into your  browser window will transform into the proper https://www.nexusmods.com address, but this is because it actively requires the data transfer protocol for communication, whether such protocol is Http or Https. 

 

As towards the removal of the protocol itself, I would suggest looking at other URLs within one's browser history.  All visited locations within mine all begin with http:// or https://    ...this whether it is here, Twitch, Nexus Mods, Verison, Mediafire or Youtube. It's just how websites are set up.

 

 

[fishburger67]

5 hours ago, LongDukDong said:

https://NexusMods.com is not a complete URL .

Incorrect.  For those who wish to go to sleep soon:

 

https://datatracker.ietf.org/doc/html/rfc1738

 

 

Edit:

 

To further clarify (or maybe confuse), try the following:

 

open a command prompt (cmd.exe) and type:

 

ping google.com

ping www.google.com

 

You will note that you get two different IP addresses, but both work (return results).

 

Then try

 

ping nexusmods.com

ping www.nexusmods.com

 

And you will get the same IP address for both URLs.

Edited July 26, 2022 by fishburger67

[PippinTom]

1 hour ago, fishburger67 said:

Then try

 

ping nexusmods.com

ping www.nexusmods.com

 

To confuse some even more - in theory, assuming specific domain configuration - pinging

 

www.nexusmods.com

and

www.NexusMods.com

 

could also return different IPs (machines).

Ergo - using anything but (recommended) lower latin letters in URLs(*) is not fancy - its at best just risky thing to do.

 

*) e-mail addresses fall under that category with same logic

[Benmc20]

On 7/25/2022 at 1:14 PM, fishburger67 said:

GET RID OF THE HTTPS:// PART AND IT WILL WORK

The "https" part works perfectly in Firefox. If Edge can't open a more secured site, throw away this browser.

[fishburger67]

9 hours ago, PippinTom said:

 

To confuse some even more - in theory, assuming specific domain configuration - pinging

 

www.nexusmods.com

and

www.NexusMods.com

 

could also return different IPs (machines).

Ergo - using anything but (recommended) lower latin letters in URLs(*) is not fancy - its at best just risky thing to do.

 

*) e-mail addresses fall under that category with same logic

Incorrect.  Case is unimportant.  See the RFC for details.

[Asrienda]

57 minutes ago, Benmc20 said:

The "https" part works perfectly in Firefox. If Edge can't open a more secured site, throw away this browser.

 

It happens in Chrome too.

 

It has nothing to do with https, it has to do with browsers auto/smart completing URLs and subdomain forwarding, like I mentioned when I first raised the issue over a week ago.

 

Both are https, they're just different sites. Fishburger is explaining it well.

 

I can of course get to loverslab, otherwise I literally wouldn't be posting here. I'm just reporting a bug in the config.

 

An answer is to just ignore it. That's not the right answer, but it's an answer.

Edited July 26, 2022 by Asrienda

[fishburger67]

9 hours ago, Asrienda said:

 

It happens in Chrome too.

 

It has nothing to do with https, it has to do with browsers auto/smart completing URLs and subdomain forwarding, like I mentioned when I first raised the issue over a week ago.

 

Both are https, they're just different sites. Fishburger is explaining it well.

 

I can of course get to loverslab, otherwise I literally wouldn't be posting here. I'm just reporting a bug in the config.

 

An answer is to just ignore it. That's not the right answer, but it's an answer.

If there is a config error, it would be in your local hosts.txt file (or maybe just hosts).  Where a request is directed is the DNS server responsible for the domain.  These requests like this make a trip to a domain name server that convert the xxx.xxx.xxx format into an ip address like 192.168.2.1 (would never be that in actual use) and then the IP address is used.  If you want to avoid any ambiguity, try

 

http://104.26.1.96

 

although in this case, Cloudflare will likely block the access.  But you can try

 

http://142.251.215.228
 

to get to google.com

 

 

Assuming that loverslab is using Apache (the most popular) but they could also use Nginx which is the second most popular.  However, the configuration of these redirects requests internally.  They would not block access if it got to it (unless it is directing a request to an asset that has been deleted).

 

The most likely would be a Cloudflare misconfiguration which I have no experience with.

 

I still think this is likely an issue on your end.  Maybe try clearing your cache (after backing it up).  Also check your hosts file if your that concerned.   In my case, I have a shortcut configured to https://www.loverslab.com so there is no ambiguity.

 

 

 

 

[Asrienda]

1 minute ago, fishburger67 said:

If there is a config error, it would be in your local hosts.txt file (or maybe just hosts).  Where a request is directed is the DNS server responsible for the domain.  These requests like this make a trip to a domain name server that convert the xxx.xxx.xxx format into an ip address like 192.168.2.1 (would never be that in actual use) and then the IP address is used.  If you want to avoid any ambiguity, try

 

http://104.26.1.96

 

although in this case, Cloudflare will likely block the access.  But you can try

 

http://142.251.215.228
 

to get to google.com

 

 

Assuming that loverslab is using Apache (the most popular) but they could also use Nginx which is the second most popular.  However, the configuration of these redirects requests internally.  They would not block access if it got to it (unless it is directing a request to an asset that has been deleted).

 

The most likely would be a Cloudflare misconfiguration which I have no experience with.

 

I still think this is likely an issue on your end.  Maybe try clearing your cache (after backing it up).  Also check your hosts file if your that concerned.   In my case, I have a shortcut configured to https://www.loverslab.com so there is no ambiguity.

 

 

 

 

 

I get the issue intermittently on both my phone on cell towers and desktop on wired internet.

[fishburger67]

Just now, Asrienda said:

 

I get the issue intermittently on both my phone on cell towers and desktop on wired internet.

That complicates the issue if you are getting it on two different devices.  Maybe Cloudflare?  I don't know.  Best choice is to just make a link like https://www.loverslab.com

 

Problem solved.  I don't believe the site admins can do anything especially with Cloudflare in the middle.

 

[shorty943]

I have had a download speed issue for a few days now on Loverslab. 

Over 1 hour to download a 129Mg file is a joke.

You guys under some kind of attack or something?

[Talesien]

1 hour ago, shorty943 said:

I have had a download speed issue for a few days now on Loverslab. 

Over 1 hour to download a 129Mg file is a joke.

You guys under some kind of attack or something?

It's not just DL speeds, opening the notification sometimes take a long time too, as does opening blogs. In short the site started to behave again like it did when one of the servers was bugged.

[Tiruil]

Cloudflare browsder check popped up again for me just now when trying to get here

[Kendo 2]

@Ashal

The cloudflare thing.

 

This is from bjornk posting over at NSFWMods.  Evidently he can't post here because of the issue he describes.  Passing it on to you.

 

Quote

This has really pissed me off which is why I'm posting about it here. After numerous time consuming experiments, I've figured that a certain "genius" at LL blocked certain user agents (i.e. browser versions) through Cloudflare and if you're accessing LL using a browser version in that list i.e. Firefox v90, v99 etc. then you're being redirected to the recaptcha page all the time, which is super annoying as it doesn't even work most of the time. If I change the user agent string to another browser or a different version of Firefox everything works fine, so it's not blocking certain IP groups or anything like that, just certain user agent strings are being blocked which is really stupid. I can't post about this there so I'd appreciate if some of you let them know about this shit.

 

[Guest]

3 hours ago, Kendo 2 said:

@Ashal

The cloudflare thing.

 

This is from bjornk posting over at NSFWMods.  Evidently he can't post here because of the issue he describes.  Passing it on to you.

 

 

That is quite interesting and thanks for reporting.

Can you ask Bjork (or whoever found the problem) to get some examples of user agent strings that are not working?

[Ashal]

There's only 2 user agents being blocked on the site via cloudflare. Both were blocked because they were outdated user agents and actively only being used by a bot attack at the time. One of them is from Internet Explorer 6 (barf), and the other a version of Chrome from 2015 (Chrome/43.0.2357.81). If either of those 2 are their current browsers, they got bigger problems than LL not working.

 

It's most likely because they are from a country that cloudflare tends to be hesitant around when security settings are set to high, which they have been for the past few days due to higher than usual traffic. It should clear up over the week as traffic returns to normal and security settings are relaxed a bit.

[worik]

12 hours ago, Tiruil said:

Cloudflare browsder check popped up again for me just now when trying to get here

It's the same annoying thing with Nexus and some other sites as well.

? I am tempted to attach the label "because politics" on that and be done with it, since it appears to be waaaaay out of my hands.

[IrvingBerlin]

Curious, and to darn lazy to read thru all the posts to check it out.   Love the changes to the site, very well done...However (you knew this was coming) the download speeds really suck, I'm downloading the latest version of WW and the current speed is 54.4 kb/sec... lots of other stuff I'd like to DL but not at these speeds....is it just me (don't thinks so because all other sites are just peachy bueno).....

 

If any of y'all can help, thanks in advance.

[shorty943]

OK, now I'm worried for the same unaccountable reason, my download speeds are now back to almost normal.

 

Thank you to which ever mod or server jockey fixed things.

[Kingfish95]

Can anyone illuminate me as to why this is happening?  Both the thread and the file have been live since December.  Why would it need approval now (as indicated by the pink triangle next to the main title?

 

Edited August 7, 2022 by Kingfish95

[Evaloves4]

> I thought at first that there was a fault from my side, but after doing several resizing my MP4 and GIF videos to minimum size LL always stretching them to the maximum. See it here although this isn't the smallest size (the smallest was 1.27 MB, I gave up from resizing my videos since the result is always the same).

Is there a way to fix it?