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

Full query only on one server #131

Open
Bleala opened this issue Nov 22, 2023 · 1 comment
Open

Full query only on one server #131

Bleala opened this issue Nov 22, 2023 · 1 comment

Comments

@Bleala
Copy link

Bleala commented Nov 22, 2023

Hello!

I discovered Hishtory this week and wanted to try it, because the features look very nice. :)

But I have one issue, the full hishtory query output is only displayed on one of my servers. On the other servers I only can see the output of this server and only of one user.

I installed it on three servers for my normal user and the root user, like it is described in the README.md.

  1. curl https://hishtory.dev/install.py | python3 -
  2. (For every server/user after the first one) hishtory init MY_SECRET

On the first server I installed everything, I can see the output from all other servers and the two user from each server.
On the other two servers I only can see the output from the specific server and user.

The hishtory status -v command output seems fine for me (the same on all servers):

hiSHtory: v0.253
Enabled: true
Secret Key: the_secret_key
User ID: the_user_id
Device ID: the_device_id
Sync Mode: Enabled
Sync Status: Synced
Commit Hash: the_commit_hash

I also tried the hishtory reupload command, which I found in another issue here, but this didn't work either.

Do you have an idea why?

I'm using the Linuxserver.io docker image with Postgres as backend, if this is important.

EDIT: I tried everything with the official server (not the LSIO docker image) and everything is working fine and as expected.
Looks like there is an issue with this docker image somewhere.

Greetings

@GRbit
Copy link
Contributor

GRbit commented Jul 24, 2024

@ddworken does it look like the issue could be closed?
TLDR: There was a problem with personal self-hosted server, but with your hishtory.dev it worked flawlessly.

Note from my side: I was able to make it work with self-hosted instance without much trouble. Most probably it was some local web server setting issue, rather than a hishtory bug.

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

2 participants