Jump to content
Sign in to follow this  
Followers 8
ErewashPaddler

Server Error on Specific cache

Recommended Posts

I've not come across this before. I am trying to look at a cache (GC8613G) which is part of a series, but although it appears as enabled I get a Server Error 500 each time I try to go into the cache from a list. I can get the icon to appear on a map, but if I click on that I get told "Sorry we couldn't find GC8613G"

Any suggestions?

Share this post


Link to post

I wonder why it shows just fine when I open it on the app.

Screenshot_20200117-020539.png

Edited by Max and 99

Share this post


Link to post

Yep! I tried opening one of my caches, GC7EN33, and I get the same error message. Gremlins!!!!!

Share this post


Link to post
2 hours ago, ErewashPaddler said:

GC8613G

Yes, I get an Error 500. I've tried from the map, from the CO search and from the cache search.

Tried on 2 windows laptops and an android tablet.

Edited by searcherdog

Share this post


Link to post

Our multicache GC7M8GW shows the same Error 500 message.
We wonder if it is related to the background picture changes.

Edited by PoeF20000
  • Upvote 1

Share this post


Link to post

image.png.4f30ddcc1c1f839c623deb824b8ea9d7.png

Correct. We've got a message by mail, but an error on our screen.

Edited by PoeF20000

Share this post


Link to post

Try a hard refresh. The 404 errors that appeared recently I could never get to load twice in a row when force-reloading the page with the error, and the same happened with occasional 500 errors that showed up. Ctrl-F5 generally does a hard refresh ignoring any cached content. Try that?

Share this post


Link to post

@PoeF20000

 

the edit page for any cache takes the guid - it's in this form:

www.geocaching.com/hide/edit.aspx?guid=

 

I can't see your darn page, but the guid loads on my "recently viewed caches" ;-)

Here's the edit page - remove the background image, see what that does?

 

https://www.geocaching.com/hide/edit.aspx?guid=baa89ea5-81b9-4281-b66e-3f3714cca1da

  • Upvote 1

Share this post


Link to post

No result. It seems logs will appear in the geocaching app. Cachepage still shows the error 500.

Share this post


Link to post

thanks for trying, that means it's a new bug, likely not related to the background image. Background image would have been simple ;-) 

Share this post


Link to post

I was able to edit the cachepage and I have deleted the background picture. No result.

Share this post


Link to post

ah, yeah the cache page is 500 for me too.

 

It may not have to do with the background, but with their excessive sanitization of listing content.

 

Interestingly, the cache does load in apps via API. And the description images are loaded from the original URL sources.  The only difference I think between the apps and the website is the whole forced parsing of the listing description on the website.  But I'm not sure what's different between this listing and others.  Unfortunately there's no way to check the background image if the web page won't load :P

Share this post


Link to post
3 minutes ago, PoeF20000 said:

I was able to edit the cachepage and I have deleted the background picture. No result.

 

How did you edit the page when it won't load?

Share this post


Link to post
19 minutes ago, Isonzo Karst said:

@PoeF20000

 

the edit page for any cache takes the guid - it's in this form:

www.geocaching.com/hide/edit.aspx?guid=

 

I can't see your darn page, but the guid loads on my "recently viewed caches" ;-)

Here's the edit page - remove the background image, see what that does?

 

https://www.geocaching.com/hide/edit.aspx?guid=baa89ea5-81b9-4281-b66e-3f3714cca1da

With the help of upper link. Isonzo, thanks. As I mentioned before, removing the bachground picture didn't solve the problem.

Edited by PoeF20000

Share this post


Link to post
17 minutes ago, PoeF20000 said:

I was able to edit the cachepage and I have deleted the background picture. No result.

 

The picture is there.  Did you put it back on the page?

 

What is the web address of these emoticons at the bottom of the cache description: "??????TheLegoCouple and Cub Fries were joint First to Find ! ??????"

 

The "?" are showing as "thumbs up" icons in The App, and question marks in GSAK (which otherwise loads the page)

 

I checked all my caches, and didn't see one that has the error. 

 

 

Edited by kunarion

Share this post


Link to post
5 minutes ago, kunarion said:

What is the web address of these emoticons at the bottom of the cache description: "??????TheLegoCouple and Cub Fries were joint First to Find ! ??????"

 

The "?" are showing as "thumbs up" icons in The App, and question marks in GSAK (which otherwise loads the page)

 

That would imply unicode emoji (more easily included in the text if editing by mobile device), and displayed entirely depending on the platform you're using. Essentially, just regular text content, and wouldn't be the cause of the 500 error (unless HQ's sanitization process is getting caught up on something; but haven't seen a 500 error for any special extended characters in descriptions at all...

Share this post


Link to post
7 minutes ago, kunarion said:

 

What is the web address of these emoticons at the bottom of the cache description: "??????TheLegoCouple and Cub Fries were joint First to Find ! ??????"

 

 

This doesn't belong  to our multi. I cann't find it in our description.

Share this post


Link to post
1 minute ago, thebruce0 said:

 

That would imply unicode emoji (more easily included in the text if editing by mobile device), and displayed entirely depending on the platform you're using. Essentially, just regular text content, and wouldn't be the cause of the 500 error (unless HQ's sanitization process is getting caught up on something; but haven't seen a 500 error for any special extended characters in descriptions at all...

 

Yeah, it's fine, it just seemed strange to me that it's just a "?" question mark within the HTML Source.  Nevermind. :cute:

Share this post


Link to post
Just now, PoeF20000 said:

This doesn't belong  to our multi. I cann't find it in our description.

 

Oh right. I copied the wrong link above. :rolleyes:

Share this post


Link to post

If there would be a problem with the content why is the cache visible in the geocaching app and not on the website and c:geo?

Share this post


Link to post
10 minutes ago, PoeF20000 said:

If there would be a problem with the content why is the cache visible in the geocaching app and not on the website and c:geo?

 

It's served in a different way.  Maybe?  I'm also seeing some differences between what the App shows and what the HTML shows on at least one of those pages.  As thebruce0 said, that might be device specific.  But if the HTML page opens fine within GSAK (it does), the code that caused the problem may also be gone -- it's just ignoring the error.  If it's content-related.

 

I tried editing a couple of the banners into my own cache page, and they're OK.

 

Edited by kunarion

Share this post


Link to post
9 minutes ago, PoeF20000 said:

If there would be a problem with the content why is the cache visible in the geocaching app and not on the website and c:geo?

 

As mentioned, the website handles all the content and serves a self-contained web page. The app gets its data streamlined from the API and displays it its own way. So it's a bug with the way the website is specifically handling the cache listing data.  Given we can see the content on mobile apps, we can guess at what the problem might be, but since it doesn't seem to be obvious, it's most likely related to some new back-end code HQ has implemented that handles displaying a geocache listing to the user.

 

If it worked before, it's not likely anything you did or changed. HQ has implemented a number of new website updates that could be affecting how the listing is being displayed. Have you contacted HQ about it yet? Sent an email to support or anything of that sort?

 

Presumably this thread will have already been noticed by a lackey at HQ, so hopefully there will be a fix or reply soon. But no guarantee.

Share this post


Link to post
39 minutes ago, PoeF20000 said:

With the help of upper link. Isonzo, thanks. As I mentioned before, removing the bachground picture didn't solve the problem.

 

If you can edit your page, you can copy all of the cache description to a new cache page and edit that. See if the error still occurs.  By removing entire blocks of code, you might discover the error.

 

Anyway, this is another thing that tends to clear up pretty quickly.  It's a server problem.  That is, you can do nothing and wait, and it clears up automagically.

 

 

Edited by kunarion

Share this post


Link to post
Just now, kunarion said:

If you can edit your page, you can copy all of the HTML to a new cache page and edit that. See if the error still occurs.  By removing entire blocks of code, you might discover the error.

 

Yep I'd recommend this in the interim. You don't even need to create a new listing - just try copying out the description source, and see what happens if the description is blank.

 

If it displays, then it's definitely something with the description text. Try adding the content back in a bit at a time. If the problem is something in the description, eventually the error will display again, and you'll know whereabouts in the text the error is being raised.  That might be something worth including in any communication you have with HQ to help them fix it.

Share this post


Link to post
11 minutes ago, thebruce0 said:

Presumably this thread will have already been noticed by a lackey at HQ, so hopefully there will be a fix or reply soon. But no guarantee.

Going through the procedure of sending a bug report I found this.

The error 500 is mentioned specifically.

 

The best way to report a bug is in the forums.

  • First see if the issue has already been reported.
  • Add new information to an existing thread.
  • Start a new thread if the bug has not yet been reported. Be sure to use a specific topic title and description. For example: "500 error when editing cache page"

Share this post


Link to post
19 minutes ago, thebruce0 said:

You don't even need to create a new listing - just try copying out the description source, and see what happens if the description is blank.

 

I just now copied everything between the main Tables in PoeF20000's cache page and edited it into a cache page, from the source code I could get in GSAK. 

And VIOLA!... Error 500.

 

OK, and yeah, now I can't edit my page.  I would have to do that direct link.  Or whatever.

 

Anyway, it looks like the code that makes the server glitch is right there in the cache description.  Wish I had time this morning to investigate that. B)

 

 

Edited by kunarion
  • Upvote 1
  • Helpful 1

Share this post


Link to post

Sounds like it just might actually have to do with the unicode text content. Maybe their updates to the HTML sanitization borked their support for unicode?

Edited by thebruce0
  • Upvote 1

Share this post


Link to post

Active again. Now I have to start adding the original listing untill it's going wrong.

Share this post


Link to post

I can edit "my" Error 500 web page using the direct link:

https://www.geocaching.com/hide/edit.aspx?guid=22248ee9-0d5b-478a-930f-652e7d407664
 

Most users probably "do not have permission" to edit that.  But if anyone higher up would like to slice and dice that (or even delete it if you want, no biggie, it's a prototype page with a completely incorrect cache description for testing), have at it!

Share this post


Link to post

Same with my "https://www.geocaching.com/geocache/GC4V6TH" get error 500.
Works fine with the geocaching app, but not on the website and c:geo.
Yesterday i saw the last log, now only the error 500.

Share this post


Link to post
1 hour ago, PoeF20000 said:

Going through the procedure of sending a bug report I found this.

The error 500 is mentioned specifically.

 

The best way to report a bug is in the forums.

  • First see if the issue has already been reported.
  • Add new information to an existing thread.
  • Start a new thread if the bug has not yet been reported. Be sure to use a specific topic title and description. For example: "500 error when editing cache page"


That's why I posted the initial problem on here - I don't actually know how to report a bug to HQ.

Share this post


Link to post

I've found the problem:

I used the following code for one of the pictures:

<center><img src="https://dagwacht.duclavier.com/PoeF20000/De%20proeflopers.png" /> <img /></center>

The latter <img /> was wrong.
It was there from the start.

 

Thank you all for your support. Learned a lot today.

  • Helpful 2

Share this post


Link to post
1 hour ago, ErewashPaddler said:

That's why I posted the initial problem on here - I don't actually know how to report a bug to HQ.

 

It's at the bottom of all cache pages …  Contact Us, and most others as well.  In the first couple sentences in Geocaching 101 too.   :)

Share this post


Link to post
18 minutes ago, PoeF20000 said:

I've found the problem:

I used the following code for one of the pictures:

<center><img src="https://dagwacht.duclavier.com/PoeF20000/De%20proeflopers.png" /> <img /></center>

The latter <img /> was wrong.
It was there from the start.

 

Thank you all for your support. Learned a lot today.

 

That's a great find! :D

Share this post


Link to post
1 hour ago, PoeF20000 said:

I used the following code for one of the pictures:

<center><img src="https://dagwacht.duclavier.com/PoeF20000/De%20proeflopers.png" /> <img /></center>

The latter <img /> was wrong.
It was there from the start.

 

Nice.

I'm sure HQ would like to know this so they can fix their description HTML sanitization routine so it doesn't die :)

Share this post


Link to post
3 hours ago, cerberus1 said:

 

It's at the bottom of all cache pages …  Contact Us, and most others as well.  In the first couple sentences in Geocaching 101 too.   :)

 

But if you go to Contact Us and say that you want to report a bug it points you to this Forum.
 

Share this post


Link to post

Please see this update from another thread:

 

25 minutes ago, nykkole said:

Thank you for reporting the broken images in the cache description. This is not related to the background image feature, but rather to another project to improve security.
 

As some of you have noted, the images were routed through a proxy server to strip them of 3rd party cookies. The expected behavior was for all images to continue to be displayed.


We have rolled this update back so that we can investigate the cause for the unintended broken images.

 

Thank you for the reports in this thread!

Share this post


Link to post

Not sure that's directly related if the issue here is the <img /> tag which doesn't relate to any provided image. This may be another but, though tangentially related if the HTML sanitization process is the commonality.

  • Upvote 1

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  
Followers 8

×
×
  • Create New...