Images point to wrong URL on Live Link

Support
1

Issue Summary

On one of my sites, the images don’t load. I noticed that the link to the image is my local URL, not the live link. ex.: http://localhost:10029/wp-content/uploads/2021/08/Pickleball-court.jpg

Troubleshooting Questions

This only happens with one site, where it had been previously working fine (earlier today).

I tested with another site and the image URL points to the live link correctly. Why would one site work and not the other?

Replication

So far I have:

  1. Stopped the site and quit LocalWP.
  2. Turned wifi off and back on.
  3. Restarted LocalWP and two sites.
  4. Enabled Live link on two sites.

One site works as it should and the other does not.

I have also cleared my browser caches, tried different browsers, private/incognito windows and also on mobile.

System Details

Local 6.0
Mac OS 11 Big Sur

Log attached
local-lightning.log (850.3 KB)

2

It’s interesting that it was previously working. Can you describe a little more about this site? For example, is it using a page builder to layout the images?

You might look at the settings for that plugin since sometimes they store data in a way that Live Links can’t transform the url.

3

Thanks, Ben. It’s just plain vanilla WordPress, no page builders. Interestingly, it was working fine again this morning and my client even noticed some adjustments as I did them.

One thing that’s possible is that yesterday I accidentally connected to my VPN while the live link was enabled. I quickly disconnected and went through the shutdown/restart process.

Is it possible that the VPN could cause the URLs to change to local?

4

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.

5

That sort of makes sense. All VPN are similar, but the specifics for how they work can be very different.

In a way Local’s live links are like a VPN – the Live link is a secure tunnel from your computer to the tunnel works that associated with your Local web account, and finally connect to the end user through that localsites.io domain.

It’s possible that when connecting to the VPN, something changed and the connection to the tunnel workers couldn’t be made directly.