Jump to content
Enpass Discussion Forum

Access to repository denied


Oceanwaves

Recommended Posts

Hello,

I'm using Enpass on Android and SuSE Tumbleweed (Desktop). Until recently access to the Enpass repository (https://yum.enpass.io/stable/x86_64/) worked fine. But now I'm getting an error "Permission denied".

I removed the repository and followed the instructions on https://support.enpass.io/app/getting_started/installing_enpass.htm to set it up again (including downloading and installing the key again), but the problem persists.

Configuration of repository:

#  | Alias                                | Name                                  | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                                 | Service
1 | Enpass                               | Enpass                                | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://
yum.enpass.io/stable/x86_64/

 

Using wget to access the URL also results in an error message:

wget https://yum.enpass.io/stable/x86_64/
--2022-07-13 15:51:40-- https://yum.enpass.io/stable/x86_64/
Resolving yum.enpass.io (yum.enpass.io)... 13.226.158.7, 13.226.158.5, 13.226.158.24, ...
Connecting to yum.enpass.io (yum.enpass.io)|13.226.158.7|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2022-07-13 15:51:41 ERROR 403: Forbidden.


Have you changed something? How can I get updates to Enpass again?

Link to comment
Share on other sites

The same problem on openSUSE 15.3 Leap! o.O

In a browser I see this: 

This XML file does not appear to have any style information associated with it. The document tree is shown below.

<Error>

<Code>AccessDenied</Code>

<Message>Access Denied</Message>

<RequestId>7H0AY8Y1MDHGTM6G</RequestId>

<HostId>276XdpVcqkUTuYD4EXYIKSi6l+F/X3B/I+m5ohqhGs/g5+zbjpsCOT6BwB91cuMHZ/1gGS6LVQk=</HostId>

</Error>

Edited by Artem
Link to comment
Share on other sites

Hi @Oceanwaves@Artem

We have updated our repository location recently. A cached DNS entry might be causing this problem. A correct nslookup output should look like this:

  1. $ nslookup -type=any yum.enpass.io
  2. Server: 127.0.0.53
  3. Address: 127.0.0.53#53
  4. Non-authoritative answer:
  5. yum.enpass.io canonical name = d1qxtbrol3w4y3.cloudfront.net.

#SI-2985

Link to comment
Share on other sites

22 hours ago, Abhishek Dewan said:

Hi @Oceanwaves@Artem

We have updated our repository location recently. A cached DNS entry might be causing this problem. A correct nslookup output should look like this:

  1. $ nslookup -type=any yum.enpass.io
  2. Server: 127.0.0.53
  3. Address: 127.0.0.53#53
  4. Non-authoritative answer:
  5. yum.enpass.io canonical name = d1qxtbrol3w4y3.cloudfront.net.

#SI-2985

Yes, that's what I get:

nslookup -type=any yum.enpass.io
Server:         192.168.178.199
Address:        192.168.178.199#53

Non-authoritative answer:
yum.enpass.io   canonical name = d1qxtbrol3w4y3.cloudfront.net.

dig gives me

dig yum.enpass.io

; <<>> DiG 9.18.4 <<>> yum.enpass.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43938
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;yum.enpass.io.                 IN      A

;; ANSWER SECTION:
yum.enpass.io.          3433    IN      CNAME   d1qxtbrol3w4y3.cloudfront.net.
d1qxtbrol3w4y3.cloudfront.net. 60 IN    A       99.84.146.21
d1qxtbrol3w4y3.cloudfront.net. 60 IN    A       99.84.146.111
d1qxtbrol3w4y3.cloudfront.net. 60 IN    A       99.84.146.93
d1qxtbrol3w4y3.cloudfront.net. 60 IN    A       99.84.146.95

 

 

Edited by Oceanwaves
Link to comment
Share on other sites

15 hours ago, Abhishek Dewan said:

Hi @all

Could you please confirm if you are able to access the following URL - Enpass yum repository?

Well, this link opens up in a browser, but first I couldn't understand this line: cd /etc/yum.repos.d/?

Another misprint is: sudo yum zypper install enpass.

And still nothing works in Yast...

Link to comment
Share on other sites

On 7/27/2022 at 4:59 AM, Artem said:

Well, this link opens up in a browser, but first I couldn't understand this line: cd /etc/yum.repos.d/?

Another misprint is: sudo yum zypper install enpass.

And still nothing works in Yast...

These are the installation instructions for a standard distribution using rpm packages and yum, you can also find it on the Enpass website describing Linux installations: https://support.enpass.io/app/getting_started/installing_enpass.htm

openSUSE 15.x as well as openSUSE Tumbleweed however use zypper instead of yum for package installation and maintenance and the instructions to set up  the repository and install Enpass using zypper are on the same page below the above mentioned installation instructions:

For openSUSE 42.3 & 15.0 #

Download and import Enpass signing key.

# wget https://yum.enpass.io/RPM-GPG-KEY-enpass-signing-key
# rpm --import RPM-GPG-KEY-enpass-signing-key

 

Add yum repo and install Enpass.

# zypper ar -f -c https://yum.enpass.io/stable/x86_64/ Enpass
# zypper update
# zypper install enpass

All they have in common is the URL (yum.enpass.io).

Link to comment
Share on other sites

I've just installed the newest version of openSUSE 15.4 on my old laptop and after a full update I installed Enpass through the routine path, noticed by Oceanwaves. It was installed easily without any issues. However, once I initiated the software update via the desktop applet I got the same response: "Permission to access denied".

Any suggestions?

 

Screenshot_20220730_121259.png

Link to comment
Share on other sites

12 hours ago, Oceanwaves said:

These are the installation instructions for a standard distribution using rpm packages and yum, you can also find it on the Enpass website describing Linux installations: https://support.enpass.io/app/getting_started/installing_enpass.htm

openSUSE 15.x as well as openSUSE Tumbleweed however use zypper instead of yum for package installation and maintenance and the instructions to set up  the repository and install Enpass using zypper are on the same page below the above mentioned installation instructions:

For openSUSE 42.3 & 15.0 #

Download and import Enpass signing key.

# wget https://yum.enpass.io/RPM-GPG-KEY-enpass-signing-key
# rpm --import RPM-GPG-KEY-enpass-signing-key

 

Add yum repo and install Enpass.

# zypper ar -f -c https://yum.enpass.io/stable/x86_64/ Enpass
# zypper update
# zypper install enpass

All they have in common is the URL (yum.enpass.io).

Thanks a lot buddy, but I follow that path every time..

Link to comment
Share on other sites

This is what I tried today:

wget https://yum.enpass.io     works (downloads index.html, which contains the instructions for installing Enpass through yum)

wget https://yum.enpass.io/enpass-yum.repo   works (downloads the yum repository)
wget https://yum.enpass.io/RPM-GPG-KEY-enpass-signing-key   works (this is the GPG key for the repository for zypper)

wget https://yum.enpass.io/stable/x86_64/enpass-6.8.1.1063-1.x86_64.rpm   works too


What I don't know: how does openSUSE 15.x/Tumbleweed check for an update to Enpass? If it simply does a check for files in yum.enpass.io/stable/x86_64/ then this will probably give an "Access denied" error now.
 

Edited by Oceanwaves
  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...
  • 3 months later...
On 8/12/2022 at 10:23 PM, Abhishek Dewan said:

Hi @Kelvino

We are still looking into this matter and will get back to you soon with an update. Your patience in the meantime is appreciated.

So, today 4 (four) months have passed. We all showed great patience. May we expect any great updates?

Thank you.

  • Like 1
Link to comment
Share on other sites

Seems to be very difficult... As a workaround I use a little script to enable the Enpass repository before checking for updates and disable it afterwards. This way I don't get error messages all the day about the repository not being accessible.

The script is for Tumbleweed:

#!/bin/bash
# Enable Enpass repository
printf "\n -------------------------------------------------------------------\n"
printf "                     Enabling Enpass repository\n"
printf " -------------------------------------------------------------------\n\n"
zypper mr -e Enpass
[...]
zypper refresh
[...]
# Dist-upgrade with no-vendor-change
zypper dup --no-allow-vendor-change
# Disable Enpass repository
printf "\n -------------------------------------------------------------------\n"
printf "                     Disabling Enpass repository\n"
printf " -------------------------------------------------------------------\n\n"
zypper mr -d Enpass

 

  • Thanks 1
Link to comment
Share on other sites

On 12/12/2022 at 7:04 PM, Oceanwaves said:

Seems to be very difficult... As a workaround I use a little script to enable the Enpass repository before checking for updates and disable it afterwards. This way I don't get error messages all the day about the repository not being accessible.

The script is for Tumbleweed:

#!/bin/bash
# Enable Enpass repository
printf "\n -------------------------------------------------------------------\n"
printf "                     Enabling Enpass repository\n"
printf " -------------------------------------------------------------------\n\n"
zypper mr -e Enpass
[...]
zypper refresh
[...]
# Dist-upgrade with no-vendor-change
zypper dup --no-allow-vendor-change
# Disable Enpass repository
printf "\n -------------------------------------------------------------------\n"
printf "                     Disabling Enpass repository\n"
printf " -------------------------------------------------------------------\n\n"
zypper mr -d Enpass

 

Great! Thanks a lot!

Link to comment
Share on other sites

  • 2 months later...

I do have the same Problem here.

I've freshly installed openSuse Leap 15.4 with all current updates and followed the install instructions for enpass (https://www.enpass.io/support/kb/general/how-to-install-enpass-on-linux/). The Update error still appears with the massage 'Permission to access 'https://yum.enpass.io/stable/x86_64/media.1/media' denied.'

Against the experience from BeamMeUp, adding the key and repo with Yast did not make a difference on my system. Maybe the switch to Tumbleweed is doing the trick, but this is not an option for me.

Edited by Taro
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...