FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have Fedora 38 and I want to install protonVPN. I followed the guide and downloaded the respective rpm package but when I try to install it or update dnf I receive this error:
Code:
ProtonVPN Fedora Stable repository 0.0 B/s | 0 B 00:00
Errors during downloading metadata for repository 'protonvpn-fedora-stable':
- Curl error (60): SSL peer certificate or SSH remote key was not OK for https://repo.protonvpn.com/fedora-38-stable/repodata/repomd.xml [SSL certificate problem: self-signed certificate in certificate chain]
Error: Failed to download metadata for repo 'protonvpn-fedora-stable': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Ignoring repositories: protonvpn-fedora-stable
Last metadata expiration check: 2:45:09 ago on Mon 05 Jun 2023 05:35:41 PM EDT.
Dependencies resolved.
Nothing to do.
Complete!
[main@fedora Downloads]$
"The error message you're receiving indicates a problem with the SSL certificate for the ProtonVPN repository. More specifically, the error "SSL certificate problem: self-signed certificate in certificate chain" suggests that there's a self-signed certificate somewhere in the certificate chain, which is generally considered insecure and can't be verified.
Here are a few possible solutions:
1. **Verify Your System Time**: An incorrect system time can cause SSL errors. Check to make sure your system time is accurate.
2. **Try Disabling SSL Verification Temporarily**: This isn't recommended for long-term solutions because it can leave your system vulnerable. But, for a quick fix or to see if SSL verification is the issue, you can try this. You'll need to modify your DNF configuration file to disable SSL verification. Here's how:
Open the DNF configuration file in a text editor with root permissions. For example, you can use `sudo` with `nano` like this:
```bash
sudo nano /etc/dnf/dnf.conf
```
Then, add or modify the `sslverify` line to be `False`:
```bash
sslverify=False
```
Save and exit the file. Then try running `sudo dnf update` again.
Remember to set `sslverify` back to `True` once you're done to keep your system secure.
3. **Contact ProtonVPN Support**: If none of the above solutions work, there might be an issue with the repository or the certificate that ProtonVPN needs to fix. Reach out to their support for help.
Remember, solution 2 is not recommended for long-term use as it disables SSL verification, which can leave your system vulnerable. It's primarily a troubleshooting step to help determine where the issue is coming from."
[main@fedora ~]$ sudo dnf install mongodb-org
MongoDB Repository 2.1 kB/s | 391 B 00:00
Errors during downloading metadata for repository 'mongodb-org-4.4':
- Status code: 404 for https://repo.mongodb.org/yum/redhat/38/mongodb-org/4.4/x86_64/repodata/repomd.xml (IP: 52.85.61.75)
Error: Failed to download metadata for repo 'mongodb-org-4.4': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
ProtonVPN Fedora Stable repository 0.0 B/s | 0 B 00:00
Errors during downloading metadata for repository 'protonvpn-fedora-stable':
- Curl error (60): SSL peer certificate or SSH remote key was not OK for https://repo.protonvpn.com/fedora-38-stable/repodata/repomd.xml [SSL certificate problem: self-signed certificate in certificate chain]
Error: Failed to download metadata for repo 'protonvpn-fedora-stable': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Ignoring repositories: mongodb-org-4.4, protonvpn-fedora-stable
Last metadata expiration check: 0:17:11 ago on Tue 06 Jun 2023 08:19:22 AM EDT.
No match for argument: mongodb-org
Error: Unable to find a match: mongodb-org
SO this is a system problem and meaning that I Just installed a fresh(sexually lewd) of Fedora 38 I don't know what I should have done or not done to address this issue so early in the life of the OS.
I have Fedora 38 and I want to install protonVPN. I followed the guide and downloaded the respective rpm package but when I try to install it or update dnf I receive this error:
Code:
ProtonVPN Fedora Stable repository 0.0 B/s | 0 B 00:00
Errors during downloading metadata for repository 'protonvpn-fedora-stable':
- Curl error (60): SSL peer certificate or SSH remote key was not OK for https://repo.protonvpn.com/fedora-38-stable/repodata/repomd.xml [SSL certificate problem: self-signed certificate in certificate chain]
Error: Failed to download metadata for repo 'protonvpn-fedora-stable': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Ignoring repositories: protonvpn-fedora-stable
Last metadata expiration check: 2:45:09 ago on Mon 05 Jun 2023 05:35:41 PM EDT.
Dependencies resolved.
Nothing to do.
Complete!
[main@fedora Downloads]$
Code:
"The error message you're receiving indicates a problem with the SSL certificate for the ProtonVPN repository. More specifically, the error "SSL certificate problem: self-signed certificate in certificate chain" suggests that there's a self-signed certificate somewhere in the certificate chain, which is generally considered insecure and can't be verified.
Here are a few possible solutions:
1. **Verify Your System Time**: An incorrect system time can cause SSL errors. Check to make sure your system time is accurate.
2. **Try Disabling SSL Verification Temporarily**: This isn't recommended for long-term solutions because it can leave your system vulnerable. But, for a quick fix or to see if SSL verification is the issue, you can try this. You'll need to modify your DNF configuration file to disable SSL verification. Here's how:
Open the DNF configuration file in a text editor with root permissions. For example, you can use `sudo` with `nano` like this:
bash sudo nano /etc/dnf/dnf.conf
Then, add or modify the `sslverify` line to be `False`:
bash sslverify=False
Save and exit the file. Then try running `sudo dnf update` again.
Remember to set `sslverify` back to `True` once you're done to keep your system secure.
3. **Contact ProtonVPN Support**: If none of the above solutions work, there might be an issue with the repository or the certificate that ProtonVPN needs to fix. Reach out to their support for help.
Remember, solution 2 is not recommended for long-term use as it disables SSL verification, which can leave your system vulnerable. It's primarily a troubleshooting step to help determine where the issue is coming from."
How can I address this?
So did you do any of those things?? Specifically step 3...calling the support you pay for??
The second problem is totally different...because it's a different website/repository, which could be down right now. Mongo DB has nothing to do with Proton VPN, and the URL you have for that repository is incorrect; just going to the base of https://repo.mongodb.org/yum/redhat shows that there IS no such path. The how-to guides are at least a year old, and have warnings on them that the information is deprecated, and will be removed. Most up to date: https://computingforgeeks.com/instal...centos-fedora/
The protonvpn 'error' is only telling you that it's a self-signed certificate.
The second problem is totally different...because it's a different website/repository, which could be down right now. Mongo DB has nothing to do with Proton VPN, and the URL you have for that repository is incorrect; just going to the base of https://repo.mongodb.org/yum/redhat shows that there IS no such path. The how-to guides are at least a year old, and have warnings on them that the information is deprecated, and will be removed. Most up to date: https://computingforgeeks.com/instal...centos-fedora/
The protonvpn 'error' is only telling you that it's a self-signed certificate.
OKay, so it is a self signed certificate? Why can't I install protonvpn then? I understand it is telling me an error but how DO I FIX IT? I mean do you know how it and you are mad that I am asking the question or are you equally as perplexed as I am.... I am confused and I am not as smart as you maybe.
OKay, so it is a self signed certificate? Why can't I install protonvpn then? I understand it is telling me an error but how DO I FIX IT? I mean do you know how it and you are mad that I am asking the question or are you equally as perplexed as I am.... I am confused and I am not as smart as you maybe.
If you feel like being snotty about things, you can try figuring things out yourself.
How you install it is by following the instructions on the Proton VPN website; step by step. You got three different things to try; again, did you try them? You can disable SSL, but again I am NOT getting an SSL issue today. Did you refresh your repositories? What, exactly, did you type in to try to install things??? Restating "I got this error" tells us nothing new; you've been asked things to help us try to help you, but haven't answered.
If you feel like being snotty about things, you can try figuring things out yourself.
How you install it is by following the instructions on the Proton VPN website; step by step. You got three different things to try; again, did you try them? You can disable SSL, but again I am NOT getting an SSL issue today. Did you refresh your repositories? What, exactly, did you type in to try to install things??? Restating "I got this error" tells us nothing new; you've been asked things to help us try to help you, but haven't answered.
Honestly since I am in prison I can't access the website protonvpn so I am going off of third party information. I don't want to disable SSL because it is a security risk. I downloaded the RPM, set it up in fedora by clicking on it and the software manager said it installed. I refreshed the repo's and it gave me the same errors. Ugh, I need to address the curl error and the url or something. IDK.
The time is correct as per date so it is not a date/time issue.
EDIT: I think it has something to do with the RPM, keys and certifications. I Think I have the wrong key or certification?? If so how would I fix that?
Honestly since I am in prison I can't access the website protonvpn so I am going off of third party information. I don't want to disable SSL because it is a security risk. I downloaded the RPM, set it up in fedora by clicking on it and the software manager said it installed. I refreshed the repo's and it gave me the same errors. Ugh, I need to address the curl error and the url or something. IDK.
The time is correct as per date so it is not a date/time issue.
Again:
You were asked what, exactly, you were typing in and haven't answered.
You were asked if you were updating your repositories, but haven't answered.
You say you can't access the protonvpn site...but you say you downloaded the RPM? How did you do that, since it's from the ProtonVPN site?? Also, what you posted says you *CAN* access the Protonvpn site, since you're getting a certificate issue. If you couldn't...you'd get a 404, but you're not.
You have a step to try as a temporary measure, but won't do it (that is, disabling SSL)
You've got things to try; either try them or not. We can't guess as to what you're doing, and just restating the CURL message tells us nothing new. If you're in prison you're going through firewalls and other proxies, which most likely will cause certificate/MITM issues. Never heard of a prison that lets inmates have their own computers, running OS'es they can't lock down/control.
You were asked what, exactly, you were typing in and haven't answered.
You were asked if you were updating your repositories, but haven't answered.
You say you can't access the protonvpn site...but you say you downloaded the RPM? How did you do that, since it's from the ProtonVPN site?? Also, what you posted says you *CAN* access the Protonvpn site, since you're getting a certificate issue. If you couldn't...you'd get a 404, but you're not.
You have a step to try as a temporary measure, but won't do it (that is, disabling SSL)
You've got things to try; either try them or not. We can't guess as to what you're doing, and just restating the CURL message tells us nothing new. If you're in prison you're going through firewalls and other proxies, which most likely will cause certificate/MITM issues. Never heard of a prison that lets inmates have their own computers, running OS'es they can't lock down/control.
"
I typed in what I Had to to install it that is "dnf uand "dnf clean-all" and "dnf update -y" and "dnf check-update". I keep getting the errors. I mean from what I typed do you have any idea what it could be? I downloaded the RPM from an email that was sent to me and this is why I need protonVPN because the internet I have is limited and secured. I shouldn't do the SSL route because it won't fix the problem over all because as with mongodb repo, I think all 3rd party repo's are going to be buggy. WHAT SHOULD I TYPE?I Will keep working on this and other task through out the day and get back to you...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
ProtonVPN not installing on Fedora 38
