Package repository for Enterprise Linux (RHEL, AlmaLinux, Rocky Linux, Oracle Linux, CentOS) and Ubuntu LTS

CodeIT is software development company (including web-based solutions). Therefore, we regularly need actual server software versions with support for advanced contemporary features. For example, NGINX and Apache httpd, built for industrial distributions with HTTP/2 and brotli compression support. But, we were not able to find ready-to-use packages. That’s why we built our own repository for RHEL/CentOS/Rocky Linux/Alma Linux/Oracle Linux distributions and you are welcome to use it:

Enterprise Linux RPM repository

Version Supported architectures Status
6.x x86_64 EOL / deprecated since 12.2020
7.x x86_64 Extended support since Jul 2024
8.x x86_64, aarch64 Supported
9.x x86_64, aarch64 Supported
10.x x86_64, aarch64 Supported

To enable automatic packages update for Linux, please be sure to configure yum repository for RHEL/CentOS distributions.

CentOS Stream is not supported, but you can manually install packages you need.

Ubuntu LTS DEB repository

Version Supported architectures Status
Ubuntu 22.04 Jammy Jellyfish x86_64, aarch64 Testing
Ubuntu 24.04 Noble Numbat x86_64, aarch64 Building

Install the Enterprise Linux RPM repository

To configure RPM repository for RHEL/CentOS, please install the following package:

CentOS 7 / RHEL 7:

Stable:
yum install -y https://repo.codeit.guru/codeit-repo-release.el7.rpm epel-release

Mainline with QUIC / HTTP/3:
yum install -y https://repo.codeit.guru/codeit-repo-release.el7.rpm epel-release && yum-config-manager --enable CodeIT-mainline --save

CentOS 8 / RHEL 8, 9, 10/ Rocky Linux 8,9, 10 / Alma Linux 8, 9, 10:

EL8: dnf install -y https://repo.codeit.guru/codeit-repo-release.el8.rpm epel-release

EL9: dnf install -y https://repo.codeit.guru/codeit-repo-release.el9.rpm epel-release

EL10: dnf install -y https://repo.codeit.guru/codeit-repo-release.el10.rpm epel-release

Mainline with QUIC stream (1.21.x, 1.23.x, …): dnf module enable -y nginx:codeit-mainline

Stable stream (1.20.x, 1.22.x): dnf module enable -y nginx:codeit-stable

Apache httpd stable: dnf module enable -y httpd:codeit

If you want to see the list of available packages, you can view the repository. Please also note that some packages in our repository rely on libraries can be found in EPEL repository (some of them are apr-util and libnghttp for Apache httpd). So, the easiest way to use our builds of  Apache HTTPd is to add EPEL repository, if you still do not have it: yum install -y epel-release

If you want to see the list of available packages, you can view the mainline repository.

Why should I use this repository?

Here we will publish the latest version of nginx (from “mainline” and “stable” branches).

CodeIT Repository for EL8, EL9, EL10 is free, donation-supported, contains SRPMs (sources). CentOS 7 support is donation-only.

Why these builds are better than official ones?

    • We built them statically against OpenSSL 4.0.0+ that contains support for ALPN (features http2 negotiation at the stage of TLS connection establishment), QUIC (HTTP/3) and TLS 1.3 RFC 8446. It is important for us, since May 2016 Google Chrome cancels NPN support. Those who have not ALPN, remain with plain HTTP/1.1 over SSL without http2.
  • Content compression support using brotli built via plug ngx_brotli + libbrotli (built as a separate package).

We’re now watching apache httpd, mod_http2, mc, nghttp2, nghttp3, ngtcp2, openssl quictls, nginx and we regularly update our buils on regular basis. In the future we plan to expand the list of software products, please check our blog regularly. Of course, SRPMs are available in the repository. Initial version is built against OpenSSL 1.0.2h. Packages in the repository are signed with our GPG-key, our public key is here.

CodeIT RPM Repository FAQ – Frequently asked questions about the CodeIT RPM Repository for RHEL-compatible Enterprise Linux systems.

1. What is the CodeIT RPM Repository?

CodeIT RPM Repository is a third-party RPM repository providing
up-to-date web server and networking packages for RHEL-compatible
Enterprise Linux distributions. It is designed for systems that need
newer versions of software such as NGINX, Apache httpd, OpenSSL,
nghttp2, nghttp3 and ngtcp2 while keeping a stable Enterprise Linux base.

2. Who is the CodeIT repository for?

It is intended for enterprise infrastructure teams, businesses,
hosting providers, DevOps and system administrators, developers,
and Linux enthusiasts who want modern web infrastructure packages
without replacing their Enterprise Linux operating system.

3. Is CodeIT RPM Repository suitable for enterprise servers?

Yes. A common use case is keeping a stable RHEL-compatible operating
system while updating selected web-stack components independently.
As with any third-party repository, organizations should test package
updates in staging and apply their normal change-management and
security-review procedures before production deployment.

4. Is the repository useful for small and medium-sized businesses?

Yes. Businesses can use standard RPM package management instead of
maintaining custom source builds of web-server software. This can make
installation, upgrades and deployment across multiple servers easier
to automate and reproduce.

5. Can individual developers and Linux enthusiasts use it?

Yes. The repository can also be used on development servers, home labs,
test environments and personal infrastructure running a compatible
Enterprise Linux distribution.

6. Which Linux distributions are supported?

The repository targets RHEL-compatible Enterprise Linux distributions,
including Red Hat Enterprise Linux, AlmaLinux, Rocky Linux and Oracle, CentOS
Linux. EL8, EL9 and EL10 are actively supported. EL7 is available under
extended-support conditions. supported.

7. Which CPU architectures are supported?

Current EL8, EL9 and EL10 repositories support x86_64 and aarch64.
EL7 packages are provided for x86_64.

8. What software is available in the CodeIT repository?

The repository focuses on modern web and networking infrastructure,
including NGINX, Apache httpd, mod_http2, OpenSSL-related packages,
nghttp2, nghttp3, ngtcp2 and related dependencies and modules.
Available versions can be checked directly in the repository index.

9. Does CodeIT support HTTP/2, HTTP/3, QUIC and modern TLS?

CodeIT builds are focused on modern web protocols and TLS features.
Packages are available for HTTP/2, TLS 1.3, Brotli and QUIC/HTTP/3
use cases. Some newer HTTP/3 functionality, particularly Apache
mod_http3 packages in the testing repository, should be considered
experimental and tested before production use.

10. Does CodeIT integrate with yum and dnf?

Yes. CodeIT is a standard RPM repository and works with the normal
yum and dnf package-management workflow. Repository release packages
are available for EL7, EL8, EL9 and EL10.

11. Can I use CodeIT with Ansible, Puppet, Chef or CI/CD automation?

Yes. Because packages are installed through standard yum and dnf
repositories, they can be managed by configuration-management and
deployment tools that support normal RPM package operations.
No CodeIT-specific deployment agent is required.

12. Can I use CodeIT on AWS, Azure, Google Cloud, VMs or bare-metal servers?

Yes. The repository is not tied to a particular hosting provider.
It can be used wherever a supported RHEL-compatible operating system
and architecture are running, including physical servers, virtual
machines and cloud instances.

13. Does CodeIT replace the standard RHEL, AlmaLinux or Rocky Linux repositories?

No. CodeIT is intended to complement the operating system repositories
by supplying selected newer web-stack and networking packages. The
underlying Enterprise Linux distribution continues to provide the
operating system and the rest of its normal packages.

14. Does CodeIT work together with EPEL?

Yes. Some CodeIT packages depend on libraries available from EPEL,
so EPEL may be installed alongside the CodeIT repository. For example,
the CodeIT installation instructions recommend enabling EPEL when
required by Apache httpd dependencies.

15. What are the alternatives to CodeIT RPM Repository?

Alternatives include using the versions supplied by the operating
system vendor, enabling other third-party repositories, using
application-vendor repositories where available, building software
from source, or running newer software inside containers. CodeIT is
particularly useful when you want normal RPM lifecycle management,
a stable Enterprise Linux base and newer web-stack packages together.

16. Why use an RPM repository instead of compiling NGINX, Apache or OpenSSL from source?

RPM packages make software easier to install, inventory, upgrade,
remove and reproduce across servers using existing Linux administration
tools. Source builds can provide similar flexibility, but organizations
must then maintain their own build process, package tracking and
deployment lifecycle.

17. Are CodeIT RPM packages signed?

Yes. Packages in the CodeIT repository are signed with GPG keys,
and the repository publishes the corresponding public keys for
package verification.

18. Are source RPMs (SRPMs) available?

Yes. Source RPMs are published alongside the repository packages,
allowing administrators and developers to inspect the packaging,
rebuild packages or adapt them for their own environments.

19. How do I get started with CodeIT RPM Repository?

Install the CodeIT repository release RPM for your Enterprise Linux
version, enable EPEL where required, and then install or enable the
package stream you need with yum or dnf. Separate repository channels
are available for stable, mainline and testing packages depending on
the software and platform.

20. Can I still use CodeIT with CentOS 7 or other EL7 systems?

EL7 is supported as an extended-support platform rather than as a
current mainstream Enterprise Linux release. Continued CentOS 7 builds
are available under CodeIT’s extended-support arrangement. For new
deployments, EL8, EL9 or EL10 should normally be preferred.

86 thoughts on “Package repository for Enterprise Linux (RHEL, AlmaLinux, Rocky Linux, Oracle Linux, CentOS) and Ubuntu LTS”

  1. Is there no changes. I followed the above procedure, actually, I’m looking for a change on this.
    Please support me.

    HTTP/1.1 200 OK
    Date: Tue, 03 Sep 2019 11:45:54 GMT
    Server: Apache/2.4.41 (codeit) PHP/7.2.22
    Last-Modified: Tue, 03 Sep 2019 11:29:11 GMT
    ETag: “1d-591a465c41698”
    Accept-Ranges: bytes
    Content-Length: 29
    Content-Type: text/html; charset=UTF-8

    Reply

  3. Hi,

    First of all thanks for your builds, during few years I’ve been using your repot to have my webservers updated.

    I’m writting this coment to request adding LUA Support for your nginx, that would enable using your builds with a lot of external third-party integrations.

    Regards,

    Reply

  6. Hello,
    please, could you build a separate package which includes support for Virtualmin?
    That is, enough to point to /home for suexec docroot, then you could explain to create a local repo and yum replace httpd –replace-with=your package

    Please, let me know, ok? thank you very much

    Reply

  7. Installed the latest from codeIT and can’t access the Apache main page on port 80:

    HTTP/1.1 403 Forbidden
    Connection: Keep-Alive
    Content-Length: 318
    Content-Type: text/html; charset=iso-8859-1
    Date: Wed, 26 Aug 2020 22:09:41 GMT
    Keep-Alive: timeout=5, max=100
    Server: Apache/2.4.46 (codeit)

    403 Forbidden

    Forbidden
    You don’t have permission to access this resource.
    Additionally, a 403 Forbidden
    error was encountered while trying to use an ErrorDocument to handle the request.

    Reply

  8. Hello,

    I still using HTTP/1 on my Centos 7 server with Magento 2.

    How can I upgrade to HTTP/2 ?

    Thanks a lot for answering

    Reply

    1. Hello,

      We do not provide support for upgrading the installations. Usually, this is easy: just upgrade the httpd package and mod_ssl with our ones, check that ssl.conf contains ciphers list and http2 protocol enabled (default sample already has everything to test it).

      However, if you are not familiar with the Apache httpd settings, please try first to play with upgrading in the test environment or hire system administrator/devops who has experience with these httpd settings.

      Reply

  9. When I run cd /etc/yum.repos.d && wget https://repo.codeit.guru/codeit.el7.repo, I get:

    –2021-01-12 15:20:51– https://repo.codeit.guru/codeit.el7.repo
    Resolving repo.codeit.guru (repo.codeit.guru)… 144.76.75.67, 2a01:4f8:191:9348::6
    Connecting to repo.codeit.guru (repo.codeit.guru)|144.76.75.67|:443… connected.
    HTTP request sent, awaiting response… 200 OK
    Length: 159 [application/octet-stream]
    codeit.el7.repo: Permission denied
    Cannot write to ‘codeit.el7.repo’ (Success).

    Is something down at the moment? Thanks!

    Reply

  11. Error: Package: mod_http2-1.15.23-1.codeit.x86_64 (CodeIT)
    Requires: libnghttp2 >= 1.21.1
    Error: Package: 1:mod_ssl-2.4.48-1.codeit.el7.x86_64 (CodeIT)
    Requires: sscg >= 2.2.0
    Error: Package: mod_http2-1.15.23-1.codeit.x86_64 (CodeIT)
    Requires: libnghttp2.so.14()(64bit)
    You could try using –skip-broken to work around the problem
    You could try running: rpm -Va –nofiles –nodigest

    i can see this error msg when i upgrade httpd and connected with
    cd /etc/yum.repos.d && wget https://repo.codeit.guru/codeit.el7.repo

    Reply

      1. I have the same problem as Sam – CentOS 7. You say “install EPEL repo” but “yum install epel-release” says there is “Nothing to do”. I have followed all steps you listed.

        Reply

        1. Marc,

          You can always recheck if you are able to install libnghttp2 1.33.0 from EPEL, if you really think that you have EPEL repo, it is enabled, libnghttp2 is not blacklisted, overrided etc.

          We do not provide support unfortunately for the operating system and only provide packages as is.

          Reply

          1. Indeed, our epel.repo was disabled!
            Thanks!

            sudo nano /etc/yum.repos.d/epel.rep
            Change enabled=0 to enabled=1

  12. Any chance to package pagespeed as a module too? Would pair really well with http/2 and brotli support.
    Cheers and thanks for your great work!

    Reply

  14. Hi just did the repos install and enable module httpd but get these errors whenever I do a dnf update this is on Almalinux 8.5

    Modular dependency problem:

    Problem: module php:7.2:8030020210119114311:2c7ca891.x86_64 requires module(httpd:2.4), but none of the providers can be installed
    – module httpd:2.4:8060020220510105858:9edba152.x86_64 conflicts with module(httpd:codeit) provided by httpd:codeit:1:el8.noarch
    – module httpd:codeit:1:el8.noarch conflicts with module(httpd:2.4) provided by httpd:2.4:8060020220510105858:9edba152.x86_64
    – module httpd:2.4:8060020220622110449:9edba152.x86_64 conflicts with module(httpd:codeit) provided by httpd:codeit:1:el8.noarch
    – module httpd:codeit:1:el8.noarch conflicts with module(httpd:2.4) provided by httpd:2.4:8060020220622110449:9edba152.x86_64
    – conflicting requests

    Reply

  15. Dependency issues.
    Transaction check error:
    file /usr/lib64/libbrotlicommon.so.1 from install of libbrotli-1.0.9-1.codeit.el7.x86_64 conflicts with file from package brotli-1.0.7-5.el7.x86_64
    file /usr/lib64/libbrotlidec.so.1 from install of libbrotli-1.0.9-1.codeit.el7.x86_64 conflicts with file from package brotli-1.0.7-5.el7.x86_64
    file /usr/lib64/libbrotlienc.so.1 from install of libbrotli-1.0.9-1.codeit.el7.x86_64 conflicts with file from package brotli-1.0.7-5.el7.x86_64

    Error Summary

    Reply

  16. Re: Dependency issue above.
    I have both apache and nginx installed. I resolved the issue by upgrading apache first.

    Reply

      1. FYI EL7 builds are already in the testing repo.
        No issues found, CI/CD and tests pass normally, so please expect OpenSSL 3 transfer in May/June.
        This will require some time where users will have broken dependencies, as soon as we do not want to change OpenSSL package name (we will keep it as openssl-quic-libs; now it is openssl-quic-libs-1.1.1t, will be openssl-quic-libs-3.0.8).
        Thus, it requires preliminary builds put to testing repos.

        Reply

  18. Hi,

    I am attempting to add the CodeIT repo as a custom repo in Red Hat Satellite 6.11. When attempting a sync of the repo, I see this error: “Katello::Errors::Pulp3Error null value in column “arch” violates not-null constraint DETAIL: Failing row contains (129f0b17-e0bc-4726-8d62-f1aeca3c912f, httpd, codeit, 1, el8, null, [{}], [“httpd-0:2.4.54-1.module_codeit.codeit.el8.x86_64”, “httpd-0:2…., f).”

    According to a support case opened with Red Hat, they reference https://access.redhat.com/solutions/7007535 where is the repo maintainer needs to set the architecture value.

    I have been using your repo for Apache web server for quite a while now and have been very satisfied with it. Perhaps I am over looking something while trying to create the repo sync in Satellite.

    Reply

    1. Hi,

      The article you provided requires a paid subscription from my side. If you can provide me with clear instructions and a test output, I would be happy to add the arch value in this case.
      createrepo --help and createrepo_mod --help do not provide any options to set this value.

      Reply

      1. Thanks for getting back. The support rep ran a test of a custom yum/dnf repo.
        Here are the steps they used and the comments made:

        ~~~
        # cat /etc/yum.repos.d/custom.repo
        [custom_repo]
        name = custom_repo
        baseurl = https://repo.codeit.guru/packages/centos/8/x86_64/
        enabled = 1
        metadata_expire = 1
        enabled_metadata = 1
        ~~~

        – Once done, run below command to check the architecture of ‘httpd’ module coming from above mentioned ‘custom_repo’.

        # dnf module info httpd

        Name : httpd
        Stream : codeit
        Version : 1
        Context : el8
        Architecture : <=========== This is BLANK
        Profiles : common
        Default profiles :
        Repo : custom_repo
        Summary : Apache httpd CodeIT Builds
        Description : Apache HTTPd server with HTTP/2, TLSv1.3, Brotli support
        Requires :

        Notice the architecture is blank above. The issue should be addressed from the maintainer of the repository. Ensure that every module in the repository has an Architecture Value set for it.

        Reply

        1. It looks like the architecture is set in the *-modules.yaml under the “data:” section
          I also use a module repo from Remi for PHP. Here is a snippet from their current YAML

          —
          document: modulemd
          version: 2
          data:
          name: php
          stream: remi-8.0
          version: 20230511155149
          context: 00000000
          arch: x86_64
          summary: PHP scripting language

          Reply

          1. Russel, thanks for pointing out!

            I used modulemd-tools 0.7 for EL8. My first thought that 0.7 can be outdated and compiled latest variant, 0.13. Unfortunately, it still did not create arch field in the module yaml despite specifying it as httpd:codeit:1:el8:aarch64:

            nsvca Module name, stream version, context and architecture
            in a N:S:V:C:A format

            Of course, I will dig it more, but if you will be able to provide any recipes for dir2module, it will be helpful.

            For this moment I don’t like the idea to patch yaml file with the simple script.

  19. Hi Alexander,

    I have been pressing Red Hat support to give me some insight to help. They have two questions.

    1. “Please confirm, In which tool CodeIT repo maintainer passing .yml file input to generate arch?”
    2. “Please confirm, CodeIT repo maintainer trying to create a custom module?”

    I appreciate your willingness work on this since I would prefer to use your repo instead of the back ported version of httpd Red Hat provides.

    Reply

    1. Hi Russel!

      1. We use “createrepo_mod” and “dir2module” tools to create the module from directory files
      2. Yes, we created custom nginx and httpd modules so users can select them and install our versions instead of RedHat ones.

      Thanks for the donation!

      Reply

    2. Please also check if EL8 builds (both x86_64 and aarch) are now parsed properly for you. Manual patching added. If it works, I will add these hacks for EL9.

      Name             : httpd
Stream           : codeit
Version          : 1
Context          : el8
Architecture     : aarch64
Profiles         : common
Default profiles :
Repo             : CodeIT
Summary          : Apache httpd CodeIT Builds
Description      : Apache HTTPd server with HTTP/2, TLSv1.3, Brotli support
      Reply

      1. Alexander,

        The latest sync worked perfectly. Thanks for working to get this going. I know it’s frustrating to manually patch. I do appreciate it.

        Reply

  20. Dear Codeit,

    we tried to sync your repo with pulp 3 but it fails within step: “Downloading Artifacts”

    traceback:
    SNIP…..
    File \”/usr/local/lib/python3.8/site-packages/pulp_rpm/app/modulemd.py\”, line 202, in parse_modular\n modulemd_all.append(create_modulemd(parsed_data, module))\n File \”/usr/local/lib/python3.8/site-packages/pulp_rpm/app/modulemd.py\”, line 120, in create_modulemd\n data[PULP_MODULE_ATTR.NAME],\n”,
    “description”: “‘name'”
    SNIP…..

    It looks like there ist some complaint about the modulemd restriction or artifacts/content regarding to the repomd. Do you have any idea?

    Reply

    1. Hello, I do not have any ideas regarding this error unfortunately. We test our repos with yum/dnf only, this is the supported way to use it.
      If you see any anomalies with other software, please report with steps to fix it.

      Reply

  21. Because Red Hat prohibits the recompilation version, it is expected that a series of versions such as almalinux will hardly survive. We also plan to migrate to the Debian platform. Are you planning to launch a corresponding package for Debian?
    Thanks.

    Reply

    1. James, why do you think that “almalinux will hardly survive”?

      Please check their blog to find official plans.

      For now I do not see any needs to support Debian for us, but anyway if community really needs it and want to support it, let’s think about it.

      Reply

      1. Alexander,
        I have seen their plans, although I also like almalinux, but I don’t think their plans will work, I don’t think their staff reserves and technical reserves and financial strength, it is really difficult to keep up with Red Hat’s bugfix and security patches, they don’t have the ability to maintain a release.
        Just a kernel patch, Red Hat can kill other recompiled versions, users will have a great sense of incompleteness, in fact, I am not willing to leave the platform that I have used for 17 years, but at present, almalinux rocky oraclelinux It’s only a matter of time before we leave.

        Reply

  22. Hi

    How can I remove codeit repo and go back to centos 7 repo? is there a way to do that?

    Reply

    1. Hi,

      Sure you can. Just remove codeit-repo package or codeit.repo file in your /etc/yum.repos.d.

      Then downgrade httpd and nginx packages to those from base vault repo.

      Please note that these downgraded versions from CentOS have known vulnerabilities.

      Reply

  23. Hello,

    Thanks for all your efforts.

    Would it be possible to create packages for spamassassin 4.0.0 (and later) for RHEL/Rocky/AlmaLinux 8 (and 9)?

    SA 4.0.0+ versions provide critical Unicode functionality, missing from earlier versions.

    Thanks,
    Nick

    Reply

    1. Hi Nick,

      CodeIT does not use spamassassin on production deployments, thus we have no plans adding SpamAssassin 4.
      At the same time, it seems we will be able to build it and add it to the pipeline to the separate repo branch on donation basis (“Great Company”+). Please tell me if you are interested.

      Reply

      1. Hi Alexander,

        I am an engineer at a non-profit public sector Scientific Research institute and I doubt that our org has the accounting flexibility to offer donations.

        What kind of donation would be considered valid?

        Cheers,
        Nick

        Reply

        1. Hi Nick,

          First of all, if you need CentOS packages, please note that CentOS 7 has finished its 10 years cycle, is considered EOL and is potentionally vulnerable.
          If you need EL7 packages and have <20 IP addresses, please use "Small Company" variant.

          You need to migrate to EL9 as soon as possible and have 8+ years of free support.

          Reply

          1. Hi Alexander,

            As I mentioned in my initial post, the server in question is currently in EL8, specifically on Rocky 8, so there is no need to migrate any time soon.

            It’s a mail gateway server (for incoming mail) with Postfix (from GhettoForge), Amavis (from EPEL), ClamAV (from EPEL), SpamAssassin (from appstream).

            Cheers,
            Nick

          2. Hi Nick,

            Sorry for the previous reply, I missed the context, now I understand that the question is in SpamAssassin rpms for EL8 and EL9.
            This requires some of work to build pipelines, support and monitoring, at the same time it will be probably used only by your organization.

            That’s why, I ask you to subscribe to “Great Company”+ package to create SA rpms flow for you (as a separate repo to avoid breaking SA for other users) even if it is a single server.
            If you have any questions, please PM me (contacts: https://codeit.guru/2024/07/centos-7-eol/).

            Thanks!

      1. Understood and thank you for the swift response.

        By joining the Patreon and supply the IP (single server) by DM, we should be able to update?

        Thank you.

        Joe

        Reply

  25. I couldn’t find any other way to contact you. I’m having an issue with access to your repository. CloudFlare is blocking access to it and yum on my server cannot complete anything with your repository enabled. This happens only from a specific IP address. Other servers in the same network range can pull https://repo.codeit.guru/packages/centos/9/x86_64/repodata/repomd.xml without any issues. Can you please take a look? Here’s a CF ray id from a curl request that I made to the above link from the problematic host: 8b7cf684a98b46ce-DFW

    Reply

    1. Hello Nikolay,

      Probably, Cloudflare resolves your source IP address as russian or belorussian. As Ukrainian based company, we do not want anyway to help aggressor and simply block these ips.

      If no, please provide this ip address, I’ll check

      Reply

      1. Thank you for reaching out to me so quickly! Can you please check the logs in your CloudFlare firewall event logs? The IP in question is located in Dallas Texas. I personally am Bulgarian and I agree with your preferences, but I don’t think that this is a place for political discussion given the fact that these comments will eventually get indexed by Google. I’ll be more than happy to continue this discussion over email if you contact me on the email that I’ve entered here as point of contact. The email address is under my personal domain name and you can quickly see where the mail server is located. I’d even share the specific IP address and WHOIS data, but not here publicly. Hope you understand.

        Reply

      2. You can easily check through Cloudflare>codeit.guru>Security>Events. There you need to add a filter, select “Ray ID” “equals” “8b7cf684a98b46ce”.

        Reply

  26. Did something change with the Centos 7 repo? My server, which is in the US, is getting a 403 forbidden error when trying to connect to it.

    Reply

  28. Dear Alexander

    I use your newest version for CentOS 9 Stream. I migrated from CentOS 7. In the newest version is it possible to use TLS 1.2 and TLS 1.3 or TLS 1.2 is disabled?

    Sincerely

    Mateusz Kiczela

    Reply

    1. Hello Mateusz,
      Sorry for the late reply.
      We do not disable anything, even TLS 1.0 and TLS 1.1 intentionally. Only when upstream disables it by default, we also do it.
      Thus, of course, TLS 1.2 is enabled.

      Reply

  29. Hi is Centos7 Repository broken? it is not browsable, nor can be added to yum available repositories without error

    Reply

      1. thanks, understood, and seriously considering supporting. Quick question, is there any option you would consider adding LUA support to your nginx compilations?

        Reply

        1. Hi Emilio,

          I see that LUA packages are a big separate world with addons like lua-resty-mysql, redis, cjson.
          Probably we can add and manage that while someone interested keeps $20/mo donation, but I am not sure we will be able to handle it for CentOS 7.

          Reply

  30. Hi,
    I am on Rocky Linux 8.
    I have installed: codeit-repo-release-1.5-1.codeit.el8.noarch
    I have executed:
    dnf –enablerepo=CodeIT,CodeIT-testing upgrade
    and I am found with these packages:
    httpd-tools-2.4.60-1_rc4.codeit.el7.x86_64
    httpd-2.4.60-1_rc4.codeit.el7.x86_64
    httpd-filesystem-2.4.60-1_rc4.codeit.el7.noarch
    mod_http2-2.0.37-1.codeit.el8.x86_64
    mod_ldap-2.4.60-1_rc4.codeit.el7.x86_64

    Questions:
    1. Why I see el7 packages? I would expect to see el8 rpms only!
    2. Why RHEL 8 Apache versions are stuck to 2.4.60 and still as an RC4? No newer versions up to 2.4.66 built yet?

    Am I doing something wrong?

    Thanks for all your efforts.

    Cheers,
    Nick

    Reply

    1. Hi Nick!
      First of all you usually don’t need to enable CodeIT-testing repo, it can be a mess, as we do not test it.
      1) Regarding EL7 packages: probably you have older .repo file in your /etc/yum.repos.d, please check
      2) There are new versions, 2.4.66. Probably you have not set up the repo as per apache httpd instruction? (dnf module enable -y httpd:codeit)?

      Reply

  31. Any chance of updating your GPG key? Rocky 9 does not support SHA1 natively and the only way to get the key to work is to lower the crypto policies.

    Reply

  32. CentOS 9 Nginx 1.29.5

    Error: Transaction test error:
    file /usr/lib64/libcrypto.so.3.5.5 from install of openssl-quic-libs-1:3.5.5-1.codeit.el9.x86_64 conflicts with file from package openssl-libs-1:3.5.5-1.el9.x86_64
    file /usr/lib64/libssl.so.3.5.5 from install of openssl-quic-libs-1:3.5.5-1.codeit.el9.x86_64 conflicts with file from package openssl-libs-1:3.5.5-1.el9.x86_64

    Reply

      1. For CentOS Stream 9 update yo nginx 1.29.5

        # dnf download openssl-quic-libs
        # dnf download openssl-libs
        # rpm -Uvh –force –nodeps openssl-quic-libs-3.5.5-1.codeit.el9.x86_64.rpm
        # rpm -Uvh –force –nodeps openssl-libs-3.5.5-1.el9.x86_64.rpm
        # dnf update nginx

        # nginx -V
        nginx version: nginx/1.29.5
        built by gcc 11.5.0 20240719 (Red Hat 11.5.0-11) (GCC)
        built with OpenSSL 3.5.4 30 Sep 2025 (running with OpenSSL 3.5.5 27 Jan 2026)
        TLS SNI support enabled
        configure arguments: –prefix=/etc/nginx –sbin-path=/usr/sbin/nginx –modules-path=/usr/lib64/nginx/modules –conf-path=/etc/nginx/nginx.conf –error-log-path=/var/log/nginx/error.log –http-log-path=/var/log/nginx/access.log –pid-path=/var/run/nginx.pid –lock-path=/var/run/nginx.lock –http-client-body-temp-path=/var/cache/nginx/client_temp –http-proxy-temp-path=/var/cache/nginx/proxy_temp –http-fastcgi-temp-path=/var/cache/nginx/fastcgi_temp –http-uwsgi-temp-path=/var/cache/nginx/uwsgi_temp –http-scgi-temp-path=/var/cache/nginx/scgi_temp –user=nginx –group=nginx –with-compat –with-file-aio –with-threads –with-http_addition_module –with-http_auth_request_module –with-http_dav_module –with-http_flv_module –with-http_gunzip_module –with-http_gzip_static_module –with-http_mp4_module –with-http_random_index_module –with-http_realip_module –with-http_secure_link_module –with-http_slice_module –with-http_ssl_module –with-http_stub_status_module –with-http_sub_module –with-http_v2_module –with-http_v3_module –with-mail –with-mail_ssl_module –with-stream –with-stream_realip_module –with-stream_ssl_module –with-stream_ssl_preread_module –add-module=modules/ngx_brotli –add-module=modules/ngx_cache_purge –add-module=modules/ngx_http_geoip2_module –with-http_v3_module –with-cc-opt=-DNGX_QUIC_OPENSSL_API=1 –with-cc-opt=’-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fPIC’ –with-ld-opt=’-Wl,-z,relro -Wl,-z,now -pie’

        Reply

Leave a Reply

Your email address will not be published. Required fields are marked *