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

Not able to connect pia frontend (client) to backend #259

Open
jtolken opened this issue Jun 4, 2024 · 0 comments
Open

Not able to connect pia frontend (client) to backend #259

jtolken opened this issue Jun 4, 2024 · 0 comments

Comments

@jtolken
Copy link

jtolken commented Jun 4, 2024

Goodevening,

first of all, let me state that i'm a storage tech. and i'm not comfortable with web stacks and many of the technologies involved in this project. So i'm sorry about having to disturb you opening this issue.

I've installed the product following the wiki but it seems i'm unable to connect the front-end client (the executable, not the server-side one) to the backend.
At the connection i get the following message

Started GET "/pias" for xxxxxxxxx at 2024-06-04 16:27:46 +0200
  ActiveRecord::SchemaMigration Pluck (0.6ms)  SELECT "schema_migrations"."version" FROM "schema_migrations" ORDER BY "schema_migrations"."version" ASC
Processing by PiasController#index as */*
Filter chain halted as :doorkeeper_authorize! rendered or redirected
Completed 401 Unauthorized in 21ms (ActiveRecord: 0.0ms | Allocations: 18055)

The page is reachable with a browser.
I think it might be a problem with Passenger since starting the applications returns

root@xxxxxxxxxxx:/var/www/pia-back# bin/rails s -b xxxxxxxxxxxxx
=> Booting Puma
=> Rails 7.0.8 application starting in development
=> Run `bin/rails server --help` for more startup options
Puma starting in single mode...
* Puma version: 5.6.8 (ruby 3.3.0-p0) ("Birdie's Version")
*  Min threads: 5
*  Max threads: 5
*  Environment: development
*          PID: 341256
* Listening on http://xxxxxxxxxxx:3000
Use Ctrl-C to stop
Started GET "/pias" for xxxxxxxxxxxxx at 2024-06-04 16:27:46 +0200

am i somehow utilizing puma instead of Passenger?

Thank you all

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

1 participant