Skip to content

Web services.
Simply looked after.

What does a 500 server error mean?

A 500 response means the server encountered a problem it could not handle while processing a request. It is a general error, not a diagnosis. Causes can involve application code, configuration, resources or connected services. The site administrator normally needs logs and the failing request’s context to investigate.

Useful context

  • Record the public page, exact time and any visible reference number.
  • Note whether the error followed a payment, booking or form submission.

How it works

  1. Preserve the request context

    Describe the action immediately before the error: opening a page, sending an enquiry or completing a purchase. Take a safe screenshot without account tokens or customer data. This lets the administrator match the report with server records instead of searching an unspecified period.

  2. Avoid repeated transactional actions

    If payment or a booking may have been processed, check the receipt or supported recovery route before trying again. An error screen does not necessarily prove the preceding operation failed. Repeated submission can create duplicates even though the visible page looks unchanged.

  3. Check the scope of the outage

    Open another ordinary public page without submitting anything. Record whether the problem affects one feature or the wider site. Check the provider’s official status information if available, while remembering that a healthy provider status does not rule out an application-specific fault.

  4. Let the maintainer use the evidence

    Send the report through the agreed support route. The maintainer should investigate the underlying error and explain the repair or remaining dependency. After a fix, repeat the relevant authorised check rather than accepting only a dashboard screenshot.

What to check

  • The report includes time, address and the preceding action.
  • Any possible payment or booking is reconciled before another attempt.
  • The actual failing journey is checked after repair.

Sources and further reading

Platform features can change. Check the provider’s current guidance before changing a live service.

A little help, when you need it

What can we help with?

Leave a message for PresGro support. This is not live chat. Please don’t include passwords or payment details.

Daily, 08:00–18:00 UK time

We aim to give an initial reply within 3–4 support hours. This is a target, not a guaranteed response or resolution time. Help outside these hours may be available.

Your details are used to respond to this enquiry. Read our privacy notice. Never send passwords. Prefer email? help@presgro.com.

Visit the support centre →