Test Topic 2 for AI Agent: File upload failed from azo

Aspose.PSD App Product Family
153

Let us know the outcome or share the additional details

154

User adds a next next post

155

Dear customer,

Thank you for your follow‑up. To investigate further we’ll need a bit more information:

  1. What specific outcome are you seeing?

    • Are you still encountering the image‑upload failure or any other error?
    • If so, please share the exact error message or HTTP status code.

  2. Steps to reproduce – a short list of actions that lead to the problem (e.g., uploading an image of a certain size, adding content while a proposal is pending, etc.).

  3. Logs / screenshots – any server logs, browser console output, or screenshots that show the failure.

  4. Attached file – if you uploaded a file with this post, could you confirm whether it opens locally and whether it is a PSD, PDF, AI, or GIF? Large or multi‑frame GIFs can cause memory issues, so reducing size or frame count often helps.

Once we have these details we can pinpoint whether the issue is a configuration limit, a bug, or something else and provide a concrete solution.

Looking forward to your clarification.

162

Dear customer,

We see that you added another post, but we’re missing the details needed to help you further. Could you please let us know:

  • What specific behavior you are observing now (e.g., error messages, failed uploads, unexpected UI changes)?
  • If this relates to the image‑size limit or to users adding content while a proposal is pending, please describe the steps you took and the result you received.
  • Any relevant logs, screenshots, or the file you are trying to upload (if the issue is still about file conversion).

With that information we’ll be able to investigate the problem and provide a concrete solution. Thank you.

163

User adds a next next post

164

User adds a next next post 4

165

User adds a next next post 6

166

User adds a next next post 5

167

Dear customer,

We see that you added another post, but we still don’t have details about the specific issue you’re encountering. Could you please provide:

  • A clear description of the problem you’re facing (e.g., upload failure, conversion error, unexpected behavior).
  • Any error messages, HTTP status codes, or logs that appear when the issue occurs.
  • The steps you followed that lead to the problem, and whether the issue is reproducible each time.
  • If you are working with a file, let us know whether the file opens correctly on your local machine and its format/size.

With that information we’ll be able to investigate further and give you a concrete solution. Thank you.

170

User adds a next next post 5

175

Dear customer,

We see that the recent posts contain only placeholder text and no additional information about the original problem (the file‑upload failure for image conversion). To be able to investigate further we’ll need some concrete details, for example:

  • The exact steps you take when the upload fails.
  • Any error message or HTTP status code shown in the UI or in the browser console.
  • The size and format of the image you are trying to upload (PSD, PNG, JPEG, etc.).
  • If a file is attached to this post, could you confirm that it opens correctly on your local machine? A corrupted file can also cause the upload to abort.
  • Relevant logs from the Discourse side (e.g., /var/discourse/log/production.log) or from the PSD‑Apps backend, if available.

With that information we can determine whether the issue is due to file size limits, unsupported format, a temporary 5xx backend error, or a configuration problem.

Please provide the above details (and any attached file) so we can help you resolve the upload failure.

176

Dear customer,

We see your latest post, but it does not contain details about the issue you are experiencing. To assist you effectively, could you please provide the following information?

  1. A clear description of the problem – what action were you performing (e.g., uploading an image, converting a file, publishing a post) and what went wrong?
  2. Any error messages or logs – copy the exact text or attach the relevant log file.
  3. Steps to reproduce – a short, numbered list of the actions that lead to the issue.
  4. Environment details – Discourse version, browser, and whether the problem occurs in development, staging, or production.

If you have a file that triggers the problem, please attach it to this post so we can test the conversion process directly.

Once we have these details we’ll be able to investigate further and provide a solution.

Thank you for your cooperation.

177

could you please provide the information?

180

Dear customer,

We understand you are looking for additional information regarding the upload issue you reported earlier. To be able to give you precise guidance, could you please provide the following details?

  1. File specifics

    • Name and extension of the file you are trying to upload (e.g., image.psd, photo.png).
    • File size (in MB).

  2. Error message / logs

    • The exact error text shown in the UI after the upload fails.
    • If possible, copy the relevant portion of the server log (e.g., a 4xx or 5xx response) or the JSON response returned by the API.

  3. Steps to reproduce

    • The sequence you follow to trigger the failure (e.g., “open the upload dialog → select file → click Convert”).
    • Whether the problem occurs with every file or only with this particular one.

  4. Environment

    • Browser and version you are using.
    • Any proxy or VPN that might affect the request.

  5. What you have tried so far

    • Clearing browser cache / using an incognito window.
    • Attempting the upload from a different browser or machine.

With this information we can verify whether the failure is due to file‑format limitations, size restrictions, a temporary backend error (5xx), or a client‑side configuration issue, and then provide the exact steps to resolve it.

Thank you for your cooperation. We look forward to your reply.

181

I am still waiting for an answer

182

Dear customer,

We’re sorry for the delay. To investigate the upload failure you’re experiencing, could you please provide the following details?

  1. File information – the exact file you are trying to upload (type, size, dimensions). If possible, attach the file to this post so we can verify that it is not corrupted.
  2. Error message – the full text shown by Discourse when the upload fails (including any HTTP status code, e.g., 5xx or 4xx).
  3. Steps to reproduce – a brief description of what you click and in which part of the UI the error occurs.
  4. Browser console log – open the developer console (F12), reproduce the upload, and copy any red‑colored messages that appear.

Common reasons for upload failures in PSD Apps include:

  • Files larger than the configured upload limit.
  • Unsupported image formats (only PSD, PNG, JPEG, GIF – keep GIFs under 5 MB).
  • Temporary backend issues (5xx responses) – retrying after a short wait often helps.

With the above information we’ll be able to pinpoint the cause and provide a concrete solution. Thank you for your patience.

183

Thank you. Fine.

184

Dear customer,

We’re glad to hear that the situation is now satisfactory. If you have any further questions, need additional details, or encounter another issue, please let us know—we’re here to help.

185

Dear customer,

We see that the upload of an image for conversion failed. Without the exact error message or any log details it’s difficult to pinpoint the cause, but common reasons for this behavior in Discourse are:

  • Unsupported or corrupted file – only PSD, PNG, JPEG, GIF (limited size) are processed. If the file is another format or is damaged the conversion job will abort.
  • File size exceeds the upload limit – the default limit is 5 MB (can be increased by an admin). Large GIFs or high‑resolution PSDs can also hit memory limits.
  • Background job failure – image conversion is performed by a Sidekiq worker. If the worker is stopped or the queue is backed‑up, the upload will appear to fail.
  • Storage or permission issues – insufficient disk space or incorrect permissions on the upload directory can cause a silent failure.
  • Temporary network/API error – a 5xx response from the storage service (e.g., S3) will also result in a failed upload.

Next steps you can take

  1. Check the exact error message that appears after the upload attempt (e.g., “Upload failed – file too large”, “Unsupported file type”, or a generic “Something went wrong”).
  2. Verify the file: open it locally to confirm it displays correctly, and note its format and size. If it’s a PSD, ensure it is not larger than a few megabytes; for GIFs keep the frame count low.
  3. Review the server logs: look for entries in production.log or Sidekiq logs around the time of the upload. Search for keywords such as upload, image conversion, or Sidekiq. Any 5xx responses or stack traces will be helpful.
  4. Confirm Sidekiq is running: run ps aux | grep sidekiq on the server or check the Discourse admin panel → Jobs to see if the image‑processing jobs are active.
  5. Check storage health: ensure the upload directory (/var/www/discourse/public/uploads) has enough free space and proper write permissions.

If the problem persists after these checks, please provide:

  • The exact error text shown in the UI.
  • The file name, type, and size you are trying to upload.
  • Relevant excerpts from production.log or Sidekiq logs (redact any sensitive data).
  • Confirmation that the issue occurs with multiple files or only this specific one.

With that information we can give a more precise diagnosis and guide you through a fix.

Let us know the details, and we’ll be happy to help you resolve the upload failure.

186

Any news about it?