Re: Re:repositories.intel.com not allowed for Ukrainian IP

liutyi · ‎08-18-2025

is that something done by mistake or is it intentional?

Amazon CloudFront distribution is configured to block access from your country

it is at least for two month that way (maybe more).

root@server3:~# curl -vvv https://repositories.intel.com/gpu/intel-graphics.key
* Host repositories.intel.com:443 was resolved.
* IPv6: (none)
* IPv4: 143.204.98.59, 143.204.98.69, 143.204.98.24, 143.204.98.9
* Trying 143.204.98.59:443...
* Connected to repositories.intel.com (143.204.98.59) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / X25519 / RSASSA-PSS
* ALPN: server accepted h2
* Server certificate:
* subject: C=US; ST=California; O=Intel Corporation; CN=repositories.intel.com
* start date: Jul 11 00:00:00 2025 GMT
* expire date: Oct 9 23:59:59 2025 GMT
* subjectAltName: host "repositories.intel.com" matched cert's "repositories.intel.com"
* issuer: C=GB; O=Sectigo Limited; CN=Sectigo Public Server Authentication CA OV R36
* SSL certificate verify ok.
* Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
* Certificate level 1: Public key type RSA (3072/128 Bits/secBits), signed using sha384WithRSAEncryption
* Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://repositories.intel.com/gpu/intel-graphics.key
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: repositories.intel.com]
* [HTTP/2] [1] [:path: /gpu/intel-graphics.key]
* [HTTP/2] [1] [user-agent: curl/8.5.0]
* [HTTP/2] [1] [accept: */*]
> GET /gpu/intel-graphics.key HTTP/2
> Host: repositories.intel.com
> User-Agent: curl/8.5.0
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
< HTTP/2 403
< server: CloudFront
< date: Mon, 18 Aug 2025 20:43:05 GMT
< content-type: text/html
< content-length: 986
< x-cache: Error from cloudfront
< via: 1.1 cdb2dba3874dd4d7b53213b8c63a0996.cloudfront.net (CloudFront)
< x-amz-cf-pop: FRA50-C1
< x-amz-cf-id: zWfL2xmaG7tlbju9BxNyPKKAH8dnEjV0qBHIyu1FJ2hP3mZnjFg2KA==
<
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>403 ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
The Amazon CloudFront distribution is configured to block access from your country.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront)
Request ID: zWfL2xmaG7tlbju9BxNyPKKAH8dnEjV0qBHIyu1FJ2hP3mZnjFg2KA==
</PRE>
<ADDRESS>
</ADDRESS>
* Connection #0 to host repositories.intel.com left intact
</BODY></HTML>

ArchieD_Intel · ‎08-19-2025

Hi liutyi,

Thank you for reaching out to the Intel Community Forum.

I've sent an email to your active email address. Please check both your Inbox and Spam folder for my email, and once received, kindly acknowledge it.

Best regards,

Archie D.

Intel Customer Support Technician

ArchieD_Intel · ‎08-20-2025

Hi liutyi,

I will thoroughly investigate the problem you encountered while attempting to access the Intel repositories.

To assist us in resolving this matter efficiently, could you please provide the following information?

What operating system and kernel version are you using?
Are you accessing the repositories to install graphics drivers? If so, could you let us know which GPU you are using?
Could you share the steps you have already taken to troubleshoot this issue? This will help us avoid repeating any efforts.

Your cooperation is greatly appreciated, and we are committed to resolving this issue promptly.

Best regards,

Archie D.

Intel Customer Support Technician

liutyi · ‎08-21-2025

What operating system and kernel version are you using?

Ubuntu 24.04 Linux (6.14.0-28-generic #28~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 25 10:47:01 UTC 2 x86_64 x86_64 x86_64 GNU/Linux)

Are you accessing the repositories to install graphics drivers? If so, could you let us know which GPU you are using?

Intel Core Ultra 9 185H iGPU (Intel Arc iGPU)

Driver installation is part of the container creation of the SD.Next-IPEX. see the file https://github.com/vladmandic/sdnext/blob/master/configs/Dockerfile.ipex

Which base image is ubuntu:noble (in case it is important)

Could you share the steps you have already taken to troubleshoot this issue? This will help us avoid repeating any efforts.

1. Add US proxy fixing the container creation - see the article https://wiki.liutyi.info/display/DEVOPS/Install+docker+SD.Next+IPEX+using+proxy+for+Intel+repo

2. curl or wget on a different Ukrainian IP gives the same 403 Forbidden

ArchieD_Intel · ‎08-21-2025

Hi liutyi,

Thank you for the feedback. I will continue to investigate this issue and will update you as soon as possible.

Best regards,

Archie D.

Intel Customer Support Technician