My character sheets are not loading image URLs

Hi. I just realized that the images I have in my character sheets, for example: <a href="https://imgsrv.roll20.net?src=https%3A//roll20.magpiegames.com/root/Root-bunny.png" rel="nofollow">https://imgsrv.roll20.net?src=https%3A//roll20.magpiegames.com/root/Root-bunny.png</a> are not displaying correctly, and when I open them in the browser, I get: <a href="https://imgsrv.roll20.net/.well-known/sgcaptcha/?r=%2Froot%2FRoot-bunny.png&amp;y=ipc:10.200.300.400:5555555555.55" rel="nofollow">https://imgsrv.roll20.net/.well-known/sgcaptcha/?r=%2Froot%2FRoot-bunny.png&amp;y=ipc:10.200.300.400:5555555555.55</a> Is this an internal Roll20 problem? Do I need to change something myself?

Hi Rober,&nbsp; Where are you hosting the images?&nbsp; Which character sheets are not working? (Sheet name and github folder address would be great)

Thanks for replying. At Magpie Games host ( <a href="http://www.magpiegames.com" rel="nofollow">www.magpiegames.com</a> ). Avatar Legends(AvatarLegendsMagpie), Root(root),.

Can you supply the links to the character sheets in github to save time hunting for them? :)

<a href="https://github.com/Roll20/roll20-character-sheets/tree/master/AvatarLegendsMagpie" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/tree/master/AvatarLegendsMagpie</a> <a href="https://github.com/Roll20/roll20-character-sheets/tree/master/root" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/tree/master/root</a> I don't have any images in the git repositories.

After looking at it briefly, it seems like maybe some bot protection on the (I think) magpiegames.com side of things might be detecting the request from Roll20's image server as bot traffic and is redirecting to this .well-known/sgcaptcha... Not 100% sure if this is on roll20's side or magpiegames but one of them is trying to display a captcha to prove the request is "human" but in this case technically it's right... roll20 has an intermediate step and doesn't directly get the images linked on the sheet.&nbsp; Easiest fix might be to just include the images in the github report and reference the raw.githubusercontent.com link to the images. *edit* Doubled checked and it looks like sitegrounds is the host of the magpiegames website... and sitegrounds is what the "sg" in "sgcaptcha" stands for. So definitely magpiegames is blocking Roll20 when it's trying to load the images. So yeah definitely moving the images into the repo is the easiest fix.

Rober said: <a href="https://github.com/Roll20/roll20-character-sheets/tree/master/AvatarLegendsMagpie" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/tree/master/AvatarLegendsMagpie</a> <a href="https://github.com/Roll20/roll20-character-sheets/tree/master/root" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/tree/master/root</a> I don't have any images in the git repositories. Thank you for providing the links. Note, I was trying to get the information you posted so that a Character Sheet coder (or someone who knows programming) like Aikepah can take a look. :)

Thank you so much for your reply. Could you help me with an example of how to use GitHub to display images? If I send the folder with images to the Roll20 repository, will it allow it, or do I have to upload them to my own repository? Aikepah said: After looking at it briefly, it seems like maybe some bot protection on the (I think) magpiegames.com side of things might be detecting the request from Roll20's image server as bot traffic and is redirecting to this .well-known/sgcaptcha... Not 100% sure if this is on roll20's side or magpiegames but one of them is trying to display a captcha to prove the request is "human" but in this case technically it's right... roll20 has an intermediate step and doesn't directly get the images linked on the sheet.&nbsp; Easiest fix might be to just include the images in the github report and reference the raw.githubusercontent.com link to the images. *edit* Doubled checked and it looks like sitegrounds is the host of the magpiegames website... and sitegrounds is what the "sg" in "sgcaptcha" stands for. So definitely magpiegames is blocking Roll20 when it's trying to load the images. So yeah definitely moving the images into the repo is the easiest fix.

Here's a pull request I did to move some images to the github repo instead of external hosting&nbsp; <a href="https://github.com/Roll20/roll20-character-sheets/pull/14589/changes#diff-d48a26e49580d1b03c1878249c848cb19edb4b214cfb2b862fb1d76c46434842" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/pull/14589/changes#diff-d48a26e49580d1b03c1878249c848cb19edb4b214cfb2b862fb1d76c46434842</a> Basically I just have a directory called images under the sheet to store all the images, and then I push them up to github. Then I get the "raw.githubusercontent.com" link to them (you can just get this from right clicking the image in the commit and copying the image URL) and in a new commit I update all the references to those images to the image's location in my github. background: url('<a href="https://raw.githubusercontent.com/aikepah/roll20-character-sheets/refs/heads/curseborne-uk-img-fix/Curseborne/images/background.png" rel="nofollow">https://raw.githubusercontent.com/aikepah/roll20-character-sheets/refs/heads/curseborne-uk-img-fix/Curseborne/images/background.png</a>'); This is where the 2nd part comes in... after that change gets merged into roll20 I can create another new branch, get the image URL's from Roll20's repo instead of mine, update all the references so they don't rely on my fork of the repo anymore.

Thanks Aiepah! I always wondered about how to manage that.

Shouldn't there be best practices to upload images to Roll20's github repository along with the character sheet code, and not to a personal user's github user folders? All it takes is for that personal user to close their github (possibly even years after stopping using Roll20 or forgetting about this place), and it would then break that character sheet for all users of it.

Thank you very much for the explanation. I will begin making these changes. Aikepah said: Here's a pull request I did to move some images to the github repo instead of external hosting&nbsp; <a href="https://github.com/Roll20/roll20-character-sheets/pull/14589/changes#diff-d48a26e49580d1b03c1878249c848cb19edb4b214cfb2b862fb1d76c46434842" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/pull/14589/changes#diff-d48a26e49580d1b03c1878249c848cb19edb4b214cfb2b862fb1d76c46434842</a> Basically I just have a directory called images under the sheet to store all the images, and then I push them up to github. Then I get the "raw.githubusercontent.com" link to them (you can just get this from right clicking the image in the commit and copying the image URL) and in a new commit I update all the references to those images to the image's location in my github. background: url('<a href="https://raw.githubusercontent.com/aikepah/roll20-character-sheets/refs/heads/curseborne-uk-img-fix/Curseborne/images/background.png" rel="nofollow">https://raw.githubusercontent.com/aikepah/roll20-character-sheets/refs/heads/curseborne-uk-img-fix/Curseborne/images/background.png</a>'); This is where the 2nd part comes in... after that change gets merged into roll20 I can create another new branch, get the image URL's from Roll20's repo instead of mine, update all the references so they don't rely on my fork of the repo anymore.

Gold said: Shouldn't there be best practices to upload images to Roll20's github repository along with the character sheet code, and not to a personal user's github user folders? All it takes is for that personal user to close their github (possibly even years after stopping using Roll20 or forgetting about this place), and it would then break that character sheet for all users of it. Aikepah's process handles that by doing it as a two step process. First linking to personal Git repo for the first merge, so that the script merges in a workable state. In the first merge, you also include all the images in the submission repo, even though they won't be used yet. Then for the second merge, you change all images links in the script to the Roll20 repo addresses. This ensures the links are always viable. They are only potentially subject to breakage until the second merge.

And to be fair, I don't think there's anything wrong with just doing it all in 1 merge with the expected location of the images in Roll20's repo. You just have to be aware that during testing you need to change where those links are pointed to so you're technically testing different code than what will actually be merged in.&nbsp; I probably will in the future change to just linking where the images will live in roll20's repo to start, just to save on the extra merge and extra commit in the original PR (one to upload images and get the URL, and one to update the URLs in the html/css). But for my own sanity and coding preferences I don't want want code up that doesn't work as a PR... I'm just so used to QA people testing my PRs and they need to be working before they get merged in haha.