You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 24, 2024. It is now read-only.
I use Linux 18.04. I installed chomper yesterday following these instructions. I got an issue at some point "Error: Couldn't install package: markupsafe", that I fixed (I guess?) by installing it from here. The rest of the install went smoothly. However, when I tried to blacklist some websites and start chomper from the CLI, nothing happened.
This morning I decided to give it a second chance. I read the documentation and used the advised command line instead of the manual installation: curl -sL https://raw.githubusercontent.com/aniketpanjwani/chomper_installers/master/debian.sh | bash && source ~/.bashrc
I then followed the instructions on the terminal to remove the existing chomper directory and install it again. I got the error again that I was missing markupsafe (honestly I can't remember if I downloaded it again or if I forgot). I also got a message that it was skipping installing the certificate (mitmproxy-ca.pem) because it already existed. I didn't think much of it, maybe I should have? It seemed normal to me since I had already installed the program once, and I remembered manually adding the certificate to firefox.
I then modified the "allon" blacklist as instructed in the documentation, started it using the CLI (chomper allon 120), and I got a success message. Great success indeed. Everything was blocked (Firefox error code: ssl_error_rx_record_too_long). However, I was still receiving messages on Discord (desktop version), although I couldn't send anything myself. Luckily, the reset command worked like a charm.
Maybe I did something wrong, I don't know much about programming yet. I just thought that I should let you know that this happened.
Edit:
I think I might have had the same issue as this one, however I didn't test different configurations of chomper.
The text was updated successfully, but these errors were encountered:
# for freeto subscribe to this conversation on GitHub.
Already have an account?
#.
I use Linux 18.04. I installed chomper yesterday following these instructions. I got an issue at some point "Error: Couldn't install package: markupsafe", that I fixed (I guess?) by installing it from here. The rest of the install went smoothly. However, when I tried to blacklist some websites and start chomper from the CLI, nothing happened.
This morning I decided to give it a second chance. I read the documentation and used the advised command line instead of the manual installation:
curl -sL https://raw.githubusercontent.com/aniketpanjwani/chomper_installers/master/debian.sh | bash && source ~/.bashrc
I then followed the instructions on the terminal to remove the existing chomper directory and install it again. I got the error again that I was missing markupsafe (honestly I can't remember if I downloaded it again or if I forgot). I also got a message that it was skipping installing the certificate (mitmproxy-ca.pem) because it already existed. I didn't think much of it, maybe I should have? It seemed normal to me since I had already installed the program once, and I remembered manually adding the certificate to firefox.
I then modified the "allon" blacklist as instructed in the documentation, started it using the CLI (
chomper allon 120
), and I got a success message. Great success indeed. Everything was blocked (Firefox error code: ssl_error_rx_record_too_long). However, I was still receiving messages on Discord (desktop version), although I couldn't send anything myself. Luckily, the reset command worked like a charm.Maybe I did something wrong, I don't know much about programming yet. I just thought that I should let you know that this happened.
Edit:
I think I might have had the same issue as this one, however I didn't test different configurations of chomper.
The text was updated successfully, but these errors were encountered: