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

Running Shaarli on Docker on a VPS: Can't login using apps but browser login works fine #1430

Closed
battlezone opened this issue Mar 8, 2020 · 7 comments
Assignees
Labels
3rd party interoperability with third-party platforms API REST API support installation and configuration issues

Comments

@battlezone
Copy link

As the title says I am running Shaarli on Docker on a VPS but I cannot login using Shaarlier or Stakali. Both say that there's a problem with authentication. When I navigate via my browser to the Shaarli instance I can login without any issue. The Shaarli logs also only show me loging in via the webpage. There are only "Login succesful" logs and nothing else.

Does anyone have an idea what I am doing wrong here? Does the communication between app and Shaarli run on a different port than 80 by any chance (Docker 8000->80)?

@nodiscc nodiscc added the support installation and configuration issues label Mar 8, 2020
@immanuelfodor
Copy link

This is definitely not a Docker issue, I'm experiencing the same after updating to the latest master. But I get login page error as well with the Material theme: kalvn/Shaarli-Material#95

@nodiscc
Copy link
Member

nodiscc commented Apr 2, 2020

Please post your full client error logs, and server access/error logs at the time of the error

@immanuelfodor
Copy link

I reverted back to my previous build of Shaarli, and as kalvn said at kalvn/Shaarli-Material#95 he indeed let the theme diverge from Shaarli master, so I feel the problem in my case is with the theme, not Shaarli core. My error log can be found at the referenced issue's OP.

@nodiscc nodiscc self-assigned this Apr 3, 2020
@nodiscc
Copy link
Member

nodiscc commented May 1, 2020

@battlezone can you still reproduce this bug?

@nodiscc nodiscc assigned battlezone and unassigned nodiscc May 1, 2020
@nodiscc nodiscc added this to the backlog to the future milestone May 1, 2020
@battlezone
Copy link
Author

@nodiscc I cannot reproduce this bug. I don't know what I've done to fix it, but it works fine now.

@ArthurHoaro
Copy link
Member

If you were talking about https://github.com/dimtion/Shaarlier, I think that @dimtion has published a new major version to use the REST API, which probably fixed your issue.

@dimtion
Copy link

dimtion commented May 28, 2020

@battlezone I can shed a bit of light on an issue I had with multiple users, that might help you find out the source of the issue.

Some web providers install in front of their instance anti-DDoS services that blocks the use of the Shaarli API. One example is to make the client solve a Javascript challenge before reaching the final page.

To find that out, you should try manually to do a request to your Shaarli instance (using Curl for example) and look if the received payload looks like a a valid JSON payload from the API.

@immanuelfodor For Shaarlier, if you are using version 1.7.2 and the token authentication there should be no issue using a personalized theme, if so, I encourage you to open an issue back in Shaarlier repo.

@nodiscc nodiscc added 3rd party interoperability with third-party platforms API REST API labels Jun 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3rd party interoperability with third-party platforms API REST API support installation and configuration issues
Projects
None yet
Development

No branches or pull requests

5 participants