Website errors

[adchris-32]

I'm trying to appeal a case at
https://www.ebay.com/ReturnCase/[case#]/AppealRequest
but there is an error in the code, so when I try to upload an image, it says: "We are unable to upload your file(s). Please try again."

All files are PNG or PDF, and under 5MB. I tried JPGs too, nothing will upload on this form. I already cleared my cache and cookies. I've tried for 2 days.

When the error occurs, I find this message under Developer Tools in Chrome:
"Request URL:
https://www.ebay.com/ItemNotReceived/ajx/UploadDocument/undefined
Request Method:
POST
Status Code:
500
Remote Address:
23.11.225.24:443
Referrer Policy:
unsafe-url"

I finally got a link to email eBay from the bot, and the email page says "We are not able to process your message now." Here is the log:

1. A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. Starting in Chrome 101, the amount of information available in the User Agent string will be reduced.

   To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.

   Note that for performance reasons, only the first access to one of the properties is shown.

2. AFFECTED RESOURCES

1 source

   email-send-id2gO1vI.js:1

1. Content Security Policy of your site blocks some resources

1. Some resources are blocked because their origin is not listed in your site's Content Security Policy (CSP). Your site's CSP is allowlist-based, so resources must be listed in the allowlist in order to be accessed.

   A site's Content Security Policy is set either via an HTTP header (recommended), or via a meta HTML tag.

   To fix this issue do one of the following:

   • (Recommended) If you're using an allowlist for 'script-src', consider switching from an allowlist CSP to a strict CSP, because strict CSPs are more robust against XSS . See how to set a strict CSP .
   • Or carefully check that all of the blocked resources are trustworthy; if they are, include their sources in the CSP of your site. ⚠️Never add a source you don't trust to your site's CSP. If you don't trust the source, consider hosting resources on your own site instead.
2. AFFECTED RESOURCES
1. 1 directive

1. Resource	Status	Directive	Source Location
   https://www.google-analytics.com/j/collect?v=1&_v=j100&a=575303227&t=pageview&_s=1&dl=https%3A%2F%2F... . . . . .

-----------------------

Until this is fixed, I cannot appeal the case. Obviously I can't talk to phone support and explain all this to a call center employee reading off a script.