https://www.finalfurlong.org/studbc.php
This page is throwing the following error:
Something went wrong! Error: 500 Please try again or report this issue if it continues.
Try it again. I had that happen to me but kept refreshing and eventually it went through.
@Shanthi – getting a 502 when I make the request. Have tried different browsers but get the same result.
Request:
GET /studbc.php HTTP/1.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.7
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-US,en;q=0.9
Cache-Control: max-age=0
Connection: keep-alive
Response:
HTTP/1.1 502 Bad Gateway
Server: nginx/1.18.0 (Ubuntu)
Date: Fri, 03 Jan 2025 02:42:50 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 89
Connection: keep-alive
ETag: “64d0b299-59”
Just want to note I have been able to nominate all my stallions without issue, both on my PC using Firefox and on my phone using Safari.
Not the same but similar - I’ve been unable to nominate horses for the BC since last year some time, all I get is a single horse at the top of the name list. Tried on Firefox and Chrome
I have the same. Also checked it in Safari and Edge, so it doesn’t seem like it’s a browser related bug.
I’ve tried Brave and Safari on my phone on both wifi and cellular. Brave, Firefox and Chrome on two separate computers. Same issue across all platforms.
Is anyone else having this issue at all, or is it just me?
I was able to nominate my two studs with no issues yesterday.
Anyone with newly retired studs (i.e. retired this year) seeing this nomination problem?
Sorry, can’t help Cat - still working on getting a stallion qualified so I can nominate 
I nominated all of our stallions early on Wednesday morning. I did have a couple of 500 Status Codes but just waited a few minutes then tried again and was successful with all of them.
I use Firefox as my browser.
@Starfish At the time, had you retired any new stallions? It’s a single page that’s the problem, not the entire website… So, the bad gateway is just confusing me. The most reasonable explanation that I can come up with for why things are in a weird state for me is that I have a new stallion (e.g. the same way hypo mating doesn’t work with newly retired studs or broodmares).
Every single time with every single browser (firefox, brave, chrome, edge) across every platform (iphone, windows laptop, linux machine) returns the same error… so, unless it’s a routing issue (and I don’t think it is – I’ve tried wifi and cellular), I really don’t think it’s an environmental issue.
I retired Death Eater after his January 1 race and nominated without issue.