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
server.crt is blank #194
Comments
Hi, the problem is that you should not run To create a new certificate now, run:
And then Normally I'd say "please open discussions instead of issues when requiring assistance". |
Thank you for the feedback alkisg. Indeed, issuing the epoptes-client -c command is what was getting me down. I was escalating user-level permissions on the client to root, which was then rewriting the server.crt file. Perhaps a note (albeit obvious) that in a chrootless LTSP environment, this command isn't required. The tailing echo of the epoptes installation is:
Perhaps adding a clause about not needing to do this step for chrootless installs. |
Closed by GSoC 2023 Epoptes improvements #204. |
Greetings, I had this working, and then upon changing my root/admin account name and directory name, I broke Epoptes. I've since corrected my root/admin account, and removed and reinstalled Epoptes while generating new .crt and key files. I'm using Ubuntu 22.04.2 using a chrootless (ltsp-pnp) install.
While I can install Epoptes and Epoptes-client, when I log into a user-level account (I've temporarily elevated them to an administrator to run
epoptes-client -c
) however, even if I log in as the user-level (non-admin) andsu - <adminuser>
and thensudo su
to get to the administrator account to runepoptes-client -c
, or provide temp admin level to the users, epoptes-client -c overwrites my /etc/epoptes/server.crtThe error that I get when running
sudo epoptes-client -c
is:Besides running chrootless, what am I doing wrong?!
Thank you in advance for your help or hints!
The text was updated successfully, but these errors were encountered: