Error 500 + non-responsive website report log

We are aware that some users are experiencing usability issues with the website, including unexpected errors and functionality problems. We understand how frustrating this can be and appreciate your patience as we investigate and try to improve the experience.

Our ability to make general improvements depends on available funding and development time, in addition to the ongoing general maintenance of the site. However, we want to prioritize investigating 500 errors and instances where the website becomes unresponsive.

The website runs on an older codebase that is not highly optimized, making it challenging to ensure smooth performance. However, we are committed to investigating these issues and doing what we can to improve stability.

How You Can Help

If you encounter a 500 error or the website becomes unresponsive, please complete the form below. Gathering these reports will help us identify patterns and potential causes.

**1. Date & Time of Issue:**
*(When did the issue occur? Please include your time zone.)*

**2. Device & Browser:**
*(Example: Windows 10 - Chrome, iPhone 13 - Safari, etc.)*

**3. Page URL:**
*(Which page were you on when the issue occurred?)*

**4. Actions Taken Before the Issue:**
*(What were you doing just before the issue occurred? Example: Submitting a form, navigating between pages, logging in, etc.)*

**5. Error Message (if any):**
*(If you saw an error message, please copy and paste it here.)*

**6. Browser Console/Network Logs (if possible):**
*(If you can, please check for errors in the browser console or network logs. You can access these by pressing F12 (Developer Tools) and clicking on the "Console" or "Network" tab. A screenshot of any errors would be helpful.)*

**7. Screenshot (if possible):**
*(Screenshots of the issue can be useful for debugging.)*

**8. Additional Information:**
*(Anything else relevant, such as whether the issue happens repeatedly or just once.)*

⚠️ Important: ⚠️ This Thread is for Reporting Only

Please do not start discussions or post anything outside of the form above. This thread is strictly for logging issues, and we will not be responding to questions or providing individual feedback here.

Our goal is to collect data to identify patterns in these errors. So far, we (the developers) have only observed some general slowness but have not been able to replicate the reported issues, which makes debugging difficult. Your detailed reports will hopefully help us pinpoint the cause and work toward a solution.

Thank you for your cooperation!

1711 GMT; Windows 11; MS Edge; an observation; attempting to add an identification; error 500
I’d overtyped and lost the alternatives from the scientific name drop box; while backing up to get the alternatives back the drop box hung. In case I’d confused the drop box I attempted to refresh the page; this resulted after a period of time in an error 500 (seen at 1714).

04/02/2025 17:10
Desktop Linux/firefox

Screen refresh following a slow down.
500 error

It’s all very well to have this form - but my errors occur regularly usually at late pm - maybe when offices are packing up and late night just before midnight.
The same pattern - I’m uploading an observation and suddenly some bits no longer link (eg drop down ID).
My test - I try logging in on a new tab and iSpot is unresponsive.
My solution has been to complete my entry and hibernate - sometimes overnight - on resumption what I have completed is not lost so all’s well that ends well. I just need to NOT PANIC - I’ve stayed with iSpot for many a year - it has so many benefits.
TODAY I was hoping to add an interaction - a fly visiting a flower posted in 2921 - coming back the link was found in seconds. Thanks iSpot - see for yourself