Certain card images not loading due to "Curl error 51"

[chasemedallion]

I have been using tabletop to play Magic, the Gathering.

Sometimes, when other players import a deck, some of the cards will not load; they will appear as blank white front and back instead. Looking at %USERPROFILE%\AppData\LocalLow\Berserk Games\Tabletop Simulator\Player.log, the only errors are "Curl error 51: Cert verify failed: UNITYTLS_X509VERIFY_FLAG_EXPIRED".

I saw some advice online for force-reloading images via CTRL+X, CTRL+V on the card; each time I do this on one of the blanks tabletop displays an "Image Error" notice in-game and then emits another Cert verify failed log entry.

Some other things I've noticed that could be relevant:
* In all the games where this has happened so far, some players CAN see the cards. Sometimes just I can't see them, whereas sometimes 2 players can't see them and 2 can.
* So far, this has only happened in the second game of the session, meaning that the first four deck imports seem to go fine and then #'s 7/8 seem to have more issues.
* Leaving the game and then returning too it does not help
* Restarting tabletop does not help

I'd appreciate any help in resolving this; it is starting to happen more often and be pretty disruptive of the experience (e. g. in my latest game this bug affected ~40% of the cards in 2 players' decks).

[ToyDragon]

I think this may be the same issue as https://forums.tabletopsimulator.com/showthread.php?8833-Redir-images-not-working-in-custom-decks , are they decks made with frogtown.me? The decks will work for users who had cached those cards prior to the TTS update that broke them. Freshly exported decks don't use redirects and should work for all players.

[scirto]

I think this may be the same issue as https://forums.tabletopsimulator.com/showthread.php?8833-Redir-images-not-working-in-custom-decks , are they decks made with frogtown.me? The decks will work for users who had cached those cards prior to the TTS update that broke them. Freshly exported decks don't use redirects and should work for all players.

Yeah this matches what I saw when posting in the other thread

EDIT: You're also right that frogtown.me was seemingly updated to not use redirect URLs for images anymore. Your suggestion of doing a fresh export of a deck works

[Demian]

This bug report is probably the same issue I am experiencing with https://imgbox.com/.

I'm getting a "WWW Image Error: Unknown Error" in-game and "Curl error 51: Cert verify failed: UNITYTLS_X509VERIFY_FLAG_EXPIRED" error in the Player.log when trying to load this URL as (for example) a custom board: https://images2.imgbox.com/e0/8a/4VgQgMiX_o.png
But no errors for this URL which loads as expected: https://images2.imgbox.com/a7/b6/ZVbyRDxH_o.png

Both images were uploaded at the same time (a long time ago) to the same service and according to the URL are served by the same server "images2". (images3 etc. are also used for other images) I can download images from both URLs with the latest version of curl and Postman for Windows 7 and I'm not seeing any warnings or oddities in the response headers. This seems to be an issue with the curl package in Tabletop Simulator since it clearly isn't a local network/firewall issue and the image host seems to be working fine?

Imgbox, however, has recently updated their URLs. For example an image used to be available at https://i.imgbox.com/5201aYVG.png which now redirects to https://images3.imgbox.com/b7/c5/5201aYVG_o.png. The latter URL also fails to load in-game.

This issue in not present only in old images. Here is an URL for an image I have uploaded to Imgbox just now (same image as above, I figured reuploading might fix the issue) and it does not load in Tabletop Simulator either: https://images2.imgbox.com/33/fa/pdD94Y4M_o.png

I cannot say for certain which version of the game broke the Imgbox URLs as I have the images cached so I would not have noticed this issue by myself. A user on Steam Workshop commented about this issue on my mod on 2020-06-14 so that's the earliest report I have of these URLs not working.

[Knil]

Next patch should have a fix for this issue we needed an engine update.

[Psillias2]

Next patch should have a fix for this issue we needed an engine update.

Are we still waiting on this? My play group and I haven't been able to play in months because of this issue.

[Demian]

This bug report is probably the same issue I am experiencing with https://imgbox.com/.

I'm getting a "WWW Image Error: Unknown Error" in-game and "Curl error 51: Cert verify failed: UNITYTLS_X509VERIFY_FLAG_EXPIRED" error in the Player.log when trying to load this URL as (for example) a custom board: https://images2.imgbox.com/e0/8a/4VgQgMiX_o.png
But no errors for this URL which loads as expected: https://images2.imgbox.com/a7/b6/ZVbyRDxH_o.png

Both images were uploaded at the same time (a long time ago) to the same service and according to the URL are served by the same server "images2". (images3 etc. are also used for other images) I can download images from both URLs with the latest version of curl and Postman for Windows 7 and I'm not seeing any warnings or oddities in the response headers. This seems to be an issue with the curl package in Tabletop Simulator since it clearly isn't a local network/firewall issue and the image host seems to be working fine?

Imgbox, however, has recently updated their URLs. For example an image used to be available at https://i.imgbox.com/5201aYVG.png which now redirects to https://images3.imgbox.com/b7/c5/5201aYVG_o.png. The latter URL also fails to load in-game.

This issue in not present only in old images. Here is an URL for an image I have uploaded to Imgbox just now (same image as above, I figured reuploading might fix the issue) and it does not load in Tabletop Simulator either: https://images2.imgbox.com/33/fa/pdD94Y4M_o.png

I cannot say for certain which version of the game broke the Imgbox URLs as I have the images cached so I would not have noticed this issue by myself. A user on Steam Workshop commented about this issue on my mod on 2020-06-14 so that's the earliest report I have of these URLs not working.

Confirming that the issue described in this message is still present as of right now on version v12.4.3.