• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.
  • 14 August 2024 It's Lightroom update time again! See What’s New in Lightroom Classic 13.5, Mobile & Desktop (August 2024)? for the bug fixes. Hopefully this will fix many of the sync issues reporting in Classic 13.3 and 13.4.

Is Jeffrey Friedl's website down? - Plug-in issue if you have upgraded to LrC 11

Status
Not open for further replies.

PhilBurton

Lightroom enthusiast (and still learning)
Premium Classic Member
Joined
Nov 16, 2015
Messages
3,319
Location
Palo Alto, California, USA
Lightroom Experience
Intermediate
Lightroom Version
Classic
Lightroom Version Number
Lightroom Classic 11.0
Operating System
  1. Windows 10
For the past two weeks I have been unable to connect to his website, for example https://regex.info/blog/

The urgency here is that all his plug-ins require a new license to work under LrC 11, or else they revert to trial mode with reduced functionality.
 
Interesting ... it seems that, as Jeffrey states, "My HTTP and HTTPS trees have been separate for decades; a browser feature that automatically assumes that all HTTP servers have an identical HTTPS server is making some very big, and in this case, wrong, assumptions."

If your web browser is set, as mine was, to "HTTPS-Only Mode" then you simply won't be able to access Jeffrey's site. I had to go into "Manage Exceptions..." and explicitly turn off HTTPS-Only mode for regex.info to gain access.
 
Like Paul my link to Goodies and the other one - Bulk Develop still work.
 
Like Paul my link to Goodies and the other one - Bulk Develop still work.
So why did I just get a 404-Not Found when I tried Paul's link?
I just tried to ping regex.info and ping could not find that site. It had no problems finding comcast.net

1635618121654.png


I know Paul is located in the UK.

@Zenon, where are you located? I may need to call my ISP (Comcast) and ask them about this issue.
 
So why did I just get a 404-Not Found when I tried Paul's link?
I just tried to ping regex.info and ping could not find that site. It had no problems finding comcast.net

View attachment 17355

I know Paul is located in the UK.

@Zenon, where are you located? I may need to call my ISP (Comcast) and ask them about this issue.
Canada
 
I used Paul's link, and it worked fine. I'm in Eastern Canada. Ping worked, too.
2021-10-30 16_18_07-Windows PowerShell.png
 
I just tried to ping regex.info and ping could not find that site.
Try a ping to 35.165.206.106 directly and see if that works from your machine.
If so, then maybe some kind of DNS lookup problem.
 
Try a ping to 35.165.206.106 directly and see if that works from your machine.
If so, then maybe some kind of DNS lookup problem.
Whaddya know. That direct IP address worked. Thanks a bunch!;)

But, but, but, when I entered that IP address into a browser bar, I got this message back. Now I'm confused.

1635638693652.png
 
Whaddya know. That direct IP address worked. Thanks a bunch!;)

But, but, but, when I entered that IP address into a browser bar, I got this message back. Now I'm confused.

View attachment 17357
As a last resort, I emailed Jeffrey Friedl, and he suggested that the browser might be set to do only SHTPPS. In fact, I had Firefox configured to do exactly that. Once I changed that browser setting, I had no problem reaching his site.

Ooops .:humble:

Phil
 
Status
Not open for further replies.
Back
Top