Let me double check to make sure it's actually going to the right domain, on the browser request

Okay, so in Media library it's pointing at the admin subdomain

admin.domain.com vs staging.domain.com, which makes me want to double check the NGINX server to make sure the subdomains are both there

Yep, they are

looks like a well formed image URL, identical to the local Valet one, same exact database

I dumped the local DB to double check there wasn't a data difference.

//admin.domain.com/img/62607402eb526/1445993007.jpg?fm=jpg&q=60&fit=max&dpr=1&h=256

Going to do a diff of the two .env files in case I'm missing something there

it should not generate a url on the admin domain though

Can you tinker twill.glide.base_url?

Are you on twill 2.8?

I'm on 2.6

I noticed when I upgraded to the latest 2.x all of my images broke locally

twill.glide.base_url is null

Ok so on 2.6, if it's null, it default to app.url, see https://github.com/area17/twill/blob/e5c3647427c3e10726476baa87caa884f0a96a8b/src/Services/MediaLibrary/Glide.php#L55

I can try GLIDE_BASE_URL and even upgrading to 2.8

GLIDE_BASE_URL should be a relative URL no? Or with the main domain?

Looks like it needs to be absolute, not just path

with the domain

path is another config

Upgrading to 2.8 my images do not break on Valet, so that's good

2.7 had an issue forcing you to use GLIDE_BASE_URL if your APP_URL was not including it's protocol

Okay, that explains why that happened

but yeah in 2.8 you don't need it, it default correctly to app_url

Okay, maybe I'll deploy with 2.8 real quick and see what happens

I'm really curious about your production 2.6 deployment rendering an admin. url though, but would be glad to hear if it works on 2.8

Still broken on production, but it's at least using staging.domain now

It actually looks like a 500 error instead of a 404, too. Which is progress

okay, it looks like it's... trying to connect to AWS for the images?

That's weird. Serving local

yeah the /img path is only registered on your frontend domain so it was not trying to do anything with it earlier. So strange that it was generating wrongly like that.