-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: "Failed to load PDF file." #1138
Comments
@andrew-opensignlabs Just picking up your comment from #159 here. The issue I am having is on Digital Ocean, LXC (Ubuntu 22.04) and MacOS ARM. I am running Ubuntu 22.04 LXC container (Proxmox). Everything is vanilla, including the I ran the same vanilla Most importantly, I am not using S3 storage in any of the environments I tested. I am only using |
Hi @bigbeka |
I'm still getting it here... Was working OK initially then stopped the service to run in detached more so I could close my terminal session (
I can see all the signed documents in my library but can't access any of them, with just an error message... |
Did you upgrade to the latest version available on docker? Additionally, it's not recommended to use local storage for storing signed files in publicly accessible production environments, as it offers lower security and creates file links that can be shared or accessed without an expiration time. |
OK I've now setup an AWS S3 bucket, added the various credentials listed at https://docs.opensignlabs.com/docs/self-host/cloud-storage/s3 to The only bit I couldn't find when following the instructions was an S3 policy for Read, Write & List so I had to just go for full access instead... I've set At the AWS end it does look like the key has at least been used: But if I tried to upload a file although it gets to 100% when I tried to submit the form I get an error: The S3 bucket itself says it has no objects. |
OK so have now changed bucket ownership to ACLs enabled and disabled CORS and it is uploading PDFs to the bucket OK but not managing to read them back, giving a 400 bad request Following the link into AWS gives the following response: <Error>
<Code>InvalidRequest</Code>
<Message>The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.</Message>
<RequestId>REDACTED</RequestId>
<HostId>REDACTED</HostId>
</Error> Could this be because older US AWS regions (I'm using |
Updated to 2.3.0 and still the same issue with 400 Bad Request |
@andrew-opensignlabs (or other maintainers) any other suggestions much appreciated! |
Updated to 2.3.2 and no change, still getting 400 Bad Request when trying to load a document. |
@EDIflyer I’ve brought this to the attention of our dev team, and if it’s confirmed as an issue, it will be resolved in next week’s release. |
Many thanks @andrew-opensignlabs - please just let me know if any more information on my setup or logs, etc required. |
Hi @andrew-opensignlabs any update on this? I saw mention of S3 in the most recent update but still having the same issue after update? |
@EDIflyer did you set CORS policy in s3? |
@andrew-opensignlabs yep, I set those previously..
Not sure if it's to do with the older encryption standard some of the US Azure instances use and an update is needed to the interface to support the more modern ones? (see link above) |
Are you still getting the same "Invalid Request" error? Or the error has changed? Try re-creating the bucket with the updated instructions. |
I'm still getting 'something went wrong' in the app and this in the console: I didn't realise you had updated your instructions. I deleted the bucket and user, re-created using the instructions at https://docs.opensignlabs.com/docs/self-host/cloud-storage/s3 and am facing exactly the same error. The only change I made to the CORS was replacing https://app.opensignlabs.com with our custom domain name. |
@EDIflyer Could you try creating the bucket in a different AWS region? I understand it’s extra work, but it will help us narrow down the issue if it works in another region. |
we are just running single command to install and configure with domain, it will configure but showing me Error when upload the pdf |
Hello, having the same issue but with a different installation. Normal users cannot access localhost:3001 and we use nginx as reverse proxy. The pdf file can be accessed successfully if localhost:3001 is changed to sign.mydomain.com manually. HOST_URL is set to https://sign.mydomain.com |
HI team,
Yes we are accessing our url: https://opensign.shipyaari.com/
with ssl certificate also ,
but we are not able to upload pdf or any image also, we are getting error.
[image: opensign.jpeg]
Please provide us with a solution.
Thanks & Regards
…On Wed, Oct 9, 2024 at 3:28 PM cube one ***@***.***> wrote:
Hello,
having the same issue but with a different installation. Normal users
cannot access localhost:3001 and we use nginx as reverse proxy. The pdf
file can be accessed successfully if localhost:3001 is changed to
sign.mydomain.com manually.
HOST_URL is set to https://sign.mydomain.com
grafik.png (view on web)
<https://github.com/user-attachments/assets/d1cdae3d-1321-4861-8ce8-4b16e89034a1>
—
Reply to this email directly, view it on GitHub
<#1138 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BLEMK7H6XB6SZ22HZMLCWDLZ2T44XAVCNFSM6AAAAABNNZX762VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBRHA3TIOJVGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I just finished installing hosting on my own VPS with vultr and I'm having the same issue fresh out of the box. |
we got this error: CORS: [ |
Hi @andrew-opensignlabs sorry for the delay in replying - on holiday just now so has taken me a while to get round to it. I created a bucked in |
Issue Description
At "Request signature", trying to place signature on to PDF, the thumbnail does not load and throws error:
Failed to load PDF file.
Docker STDOUT:
Expected Behavior
It should load the thumbnail of the pdf and its pages.
Current Behavior
Error:
Failed to load PDF file.
Steps to reproduce
export HOST_URL=https://sign.FQDN.io && curl --remote-name-all https://raw.githubusercontent.com/OpenSignLabs/OpenSign/docker_beta/docker-compose.yml https://raw.githubusercontent.com/OpenSignLabs/OpenSign/docker_beta/Caddyfile https://raw.githubusercontent.com/OpenSignLabs/OpenSign/docker_beta/.env.local_dev && mv .env.local_dev .env.prod && docker compose up --force-recreate
Request signatures
Request signatures
, the PDF does not loadScreenshots of the issue(optional)
Operating System [e.g. MacOS Sonoma 14.1, Windows 11]
Ubuntu 24.04
What browsers are you seeing the problem on?
Safari
What version of OpenSign™ are you seeing this issue on? [e.g. 1.0.6]
Latest [version: v2.2.0]
What environment are you seeing the problem on?
Production (app.opensignlabs.com)
Please check the boxes that apply to this issue report.
Code of Conduct
The text was updated successfully, but these errors were encountered: