Custom Domain serves old version of site / 404

[ltickett]

Before opening, please confirm:

• [X] I have checked the custom domains troubleshooting guide.
• [X] I have read the guide for submitting bug reports.
• [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id

dlitcjrqaqz64

Region

eu-west-1

Step

Custom Domain

Status

Confused

Issue or question

I have setup continuous deployment to Amplify and things seem to be working nicely.

I can see the date/time of the last deployment in a version.html file I include in the deployment:

https://prod.dlitcjrqaqz64.amplifyapp.com/version.html

Unfortunately, when I try and access the file via my custom domain I get a 404:

https://fp.tickett.net/version.html

I have another Amplify app and am seeing "similar" behaviour (for that app, I am actually seeing an old version of the version.html when using my custom domain, but the current deployment when using the .amplifyapp.com domain).

Any bright ideas?

Many Thanks!

Error message

No response

Additional information

No response

[ghost]

Hi @ltickett 👋🏽 thanks for raising this issue. I'm not sure what caused this behavior but while we investigate, try removing the domain, adding it back, and then redeploy. Please let us know if this unblocks you.

[ltickett]

Thanks @hloriana I gave that a try, but it didn't help unfortunately.

I hope you are able to identify the issue your end.

[ghost]

@ltickett I'm seeing a 200 response on your site now. Is it returning the updated version.html file?

[ltickett]

Nope, still seeing an error though I now realise it's not a 404

Does this help?

Thanks @hloriana

[ltickett]

I just rechecked and now the page is loading and matches between the amplifyapp.com address and fp.tickett.net

So I decided to try deploying a new version...

That is immediately reflected on the amplifyapp.com address, but fp.tickett.net is still showing the old one.

Driving me insane!

[ghost]

Okay yes I can now see that the custom domain and the amplify domain are now showing 2 different versions. We are investigating what is causing the delay.

[ltickett]

Really glad you've been able to recreate. I hope I'm not doing something silly.

It seems like a super straightforward config/setup.

Thanks for keeping me in the loop.

[ltickett]

Any joy @hloriana ?

I feel like I may have to jump ship soon if we can't figure out what's going on :/

[Narrator]

@ltickett Hello! I'm an engineer from the Amplify team.

It looks like you are deploying using a custom URL. We have a known issue with this mechanism and we have a fix for this in the pipeline that should get deployed next week.

Meanwhile, here are some manual workarounds (You won't be able to use your continuous deployment process):

1. Upload your zip file to S3 and start a build on the Amplify console by providing the details of the S3 bucket.
2. Drag and drop the zip file via the Amplify console

You can read more about these methods by following this link: https://docs.aws.amazon.com/amplify/latest/userguide/manual-deploys.html

[ltickett]

Super, thanks @Narrator

Is this known issue documented publicly? It might have saved me a lot of wasted effort.

Similarly, where can I follow along to see the status of the fix?

Many Thanks

L

[Narrator]

@ltickett

This issue is not publicly documented right now, but we have been tracking it internally.

We can use this Github issue to track the status of the fix. We will notify you as soon as the fix is rolled out. Thanks for your patience!

[ltickett]

@Narrator any progress? Are you still optimistic we'll get this resolved by the end of the week?

Thanks

L

[ltickett]

Hi @Narrator - just checking in to see if you have an update please?

[Narrator]

@ltickett The fix has been rolled out! Can you please try your deployment now and let us know if there are any issues? Thanks for your patience!

[ltickett]

Bad news unfortunately @Narrator

The issue still seems to exist.

Let me know if you need any further detail.

Thanks

L

[ltickett]

It's looking OK now from my laptop (my phone is still showing the access denied message, though works in incognito, so I guess some browser caching might be going on).

I just tried with another Amplify site, and that seems to be working too.

Great job- thank you!

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.