SMT Azure Server Permission Denied/403 Forbidden

Hi All,

We get the following error when trying to access the SMT Server
Permission to access 'https://smt-azure.susecloud.net/repo/SUSE/Updates/SLE-Module-Adv-Systems-Management/12/x86_64/update/repodata/repomd.xml?credentials=Advanced_Systems_Management_Module_x86_64'; denied.

also I have noticed we get a 403 denied error when trying to wget the domain

`wget -d https://smt-azure.susecloud.net
DEBUG output created by Wget 1.14 on linux-gnu.

URI encoding = ‘UTF-8’
asking libproxy about url 'https://smt-azure.susecloud.net/'
libproxy suggest to use 'direct://'
--2020-09-30 10:52:17-- https://smt-azure.susecloud.net/
Resolving smt-azure.susecloud.net (smt-azure.susecloud.net)... 52.188.81.163
Caching smt-azure.susecloud.net => 52.188.81.163
Connecting to smt-azure.susecloud.net (smt-azure.susecloud.net)|52.188.81.163|:443... connected.
Created socket 3.
Releasing 0x00000000026f4e00 (new refcount 1).
Initiating SSL handshake.
Handshake successful; connected socket 3 to SSL handle 0x00000000026e3a40
certificate:
subject: /C=DE/ST=Bavaria/L=Nuremberg/O=SUSE/OU=Public Cloud/CN=Update server certificate (smt-azure.susecloud.net)/emailAddress=suse-public-cloud@susecloud.net
issuer: /C=DE/ST=Bavaria/L=Nuremberg/O=SUSE/OU=CSM/CN=SUSE/emailAddress=suse-public-cloud@susecloud.net
X509 certificate successfully verified and matches host smt-azure.susecloud.net

---request begin---
GET / HTTP/1.1
User-Agent: Wget/1.14 (linux-gnu)
Accept: /
Host: smt-azure.susecloud.net
Connection: Keep-Alive

---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 403 Forbidden
Server: nginx/1.14.2
Date: Wed, 30 Sep 2020 10:51:16 GMT
Content-Type: text/html
Content-Length: 169
Connection: keep-alive

---response end---
403 Forbidden
Registered socket 3 for persistent reuse.
Skipping 169 bytes of body: [
403 Forbidden

403 Forbidden


nginx/1.14.2



] done.
2020-09-30 10:52:17 ERROR 403: Forbidden.`

Has anyone experienced this before? we have only came across this error recently in the past week or so and its been intermittent, prior to this everything seemed to work fine.

Thanks,
Kav

Comments

Sign In or Register to comment.