If your next.js application dynamically adds images to /public during runtime, the image will exist in the correct spot, but when loaded produces an error
⨯ The requested resource isn't a valid image for /images/player_heads/e281289d-4eff-4851-9cb5-8fc3388dee7e.png received text/html; charset=utf-8
restarting the application fixes it. And it only happens when running in production, but in dev it works how you would expect.

Bug....? So then how would you dynamically serve images that may not exist when starting the server.....?