Skip to content
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

Upgrade to v1.4.2 failed #559

Open
sherlant opened this issue Apr 4, 2024 · 7 comments
Open

Upgrade to v1.4.2 failed #559

sherlant opened this issue Apr 4, 2024 · 7 comments
Assignees

Comments

@sherlant
Copy link

sherlant commented Apr 4, 2024

Hi,
i have try to upgrade my opensign instance from v1.2.2-beta to v1.4.2.
After the upgrade, i've try to retrieve my password my the forgot password button, but when i submit with my email, a popup tell me that i must configure an email adapter.
I have already setup SMTP configuration, and the configuration was OK in v1.2.2-beta.
In the new documentation, i don't see SMTP configuration, only with MAILGUN_API_KEY/MAILGUN_DOMAIN/MAILGUN_SENDER, i have try to modify my configuration with this env vars, same result.
I have try to create a new user too, and i have an other error when i submit the form :

XMLHttpRequest failed: "SyntaxError: Unexpected token '<', \"<!doctype \"... is not valid JSON"

Can you help me please ?

@sherlant
Copy link
Author

Hello,
this issue still with v1.5.1.

Any update ?

@nxglabs
Copy link
Contributor

nxglabs commented Apr 26, 2024

Can you share the opensign-server logs when you encounter this error?

@sherlant
Copy link
Author

sorry, there are nothing in logs when i have the error in web ui. The only logs are in the server starting :


> [email protected] start
> node index.js

(node:21) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
(node:21) NOTE: The AWS SDK for JavaScript (v2) will enter maintenance mode
on September 8, 2024 and reach end-of-support on September 8, 2025.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check blog post at https://a.co/cUPnyil
parse-server-example running on port 8080.
Command output: 
Parse DBTool v1.2.0 - Parse server tool for data migration and seeding.

Run migration on parse-server at http://localhost:8080/app

 ⠶ Migrating 20240408133151-update_contracts_document_cls.cjs
 ✓ Migrated  20240408133151-update_contracts_document_cls.cjs


 SUCCESS  Successfully run migrations.

@sherlant
Copy link
Author

sherlant commented May 21, 2024

Hi,
i have try to deploy opensign in latest version (v1.7.2) from scratch.
After the deploy, i find two issues :

  • The logs in opensign-server at start :

> [email protected] start
> node index.js

(node:21) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
(node:21) NOTE: The AWS SDK for JavaScript (v2) will enter maintenance mode
on September 8, 2024 and reach end-of-support on September 8, 2025.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check blog post at https://a.co/cUPnyil
parse-server-example running on port 8080.

WARNING, Unable to connect to 'http://localhost:8080/app'. Cloud code and push notifications may be unavailable!

Error: Command failed: APPLICATION_ID=XXXXXXX SERVER_URL=http://localhost:8080/app MASTER_KEY=XXXXXXX npx parse-dbtool migrate
parse-dbtool migrate

Run migrations

Options:
      --version  Show version number                                   [boolean]
  -h, --help     Show help                                             [boolean]

ParseError: XMLHttpRequest failed: "Unable to connect to the Parse API"
    at handleError (/usr/src/app/node_modules/parse-dbtool/node_modules/parse/lib/node/RESTController.js:425:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Promise.all (index 0)
    at async /usr/src/app/node_modules/parse-dbtool/node_modules/parse/lib/node/ParseQuery.js:1177:25
    at async ParseQuery.findAll (/usr/src/app/node_modules/parse-dbtool/node_modules/parse/lib/node/ParseQuery.js:853:5)
    at async getAllRunMigrations (/usr/src/app/node_modules/parse-dbtool/src/libs/migration-model.js:38:22)
    at async getAllMigrations (/usr/src/app/node_modules/parse-dbtool/src/libs/migration-model.js:69:28)
    at async migrationUp (/usr/src/app/node_modules/parse-dbtool/src/migration-up.js:38:27)
    at async Object.migrationUpHandler [as handler] (/usr/src/app/node_modules/parse-dbtool/src/migration-up.js:85:25) {
  code: 100
}

i have try to curl directly the server in the container, and this is ok :

# curl http://localhost:8080
open-sign-server is running !!!

# curl http://localhost:8080/app
{"error":"unauthorized"}
  • in the ui, when i try to create a new account, i have the same error :
XMLHttpRequest failed: "SyntaxError: Unexpected token '<', \"<!doctype \"... is not valid JSON"

@Zathiel
Copy link
Collaborator

Zathiel commented Jun 2, 2024

Hey @sherlant

Are you still facing issues with the last release ?

If not i will mark this issue as solved

@Zathiel Zathiel self-assigned this Jun 2, 2024
@sherlant
Copy link
Author

sherlant commented Jun 3, 2024

Hello,
Yes, i have just try with v1.7.3 (from scratch), and both errors in server and in client when i create account still

@dgilsonAfelio
Copy link

I got the exact same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants