An error occurred during a connection to localhost:10004. SSL received a record that exceeded the maximum permissible length.
Error code: SSL_ERROR_RX_RECORD_TOO_LONG
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
Thanks for these articles.
However, there is no Trust link (see attached screenshot).
The message “SSL Note! HTTPS is not available when using the localhost Routing Mode” and what is occurring, are confusing.
Are you able to create a new site in Local with default settings, and successfully enable SSL (following the guide I sent above)?
If so, I’m wondering if maybe something about your imported site is redirecting http:// to https:// (like a plugin or override in a file) and causing issues.
Hi Sam, i restarted Local, and attempted to trust “test” again, and again, got the error.
In keychain I found test.local and set the Trust to always.
On returning to Local, test is now trusted.
Then I went back to woodmood and it is also trusted.
However, when I attempt to open the site, I get “there is a port conflict with the site’s domain”.
I ran activity monitor and com.apple.geod appears to be listening on port 80.
It appears that port 80 is used by numerous apple services: TCP and UDP ports used by Apple software products - Apple Support
When I attempt to open site, I am taken to woodmood.local and the page displays “unknown app”.
if I type “localhost:80” into the URL bar I also get “unknown app”.
Thank you for all of these details, it’s very helpful to see the various things you tried along the way.
Reading through - it sounds like switching router mode back to localhost everything is working okay, correct?
Yes, I think there might be an issue with something conflicting with Local (specifically when you’re in the Site domains mode, which allows you to use SSL).
Have you attempted to reboot your machine?
I’m looking at a similar thread about a port conflict with MacOS and this user found success after a reboot:
Thanks for that article—using lsof I found the process.
I could kick myself—I’m a Rails developer and I had puma-dev running as a background job.
Killing and unloading it did the trick!