CodeIT repository: RPM and DEB packages of NGINX, Apache httpd with HTTP/3 and OpenSSL for RHEL and Ubuntu

95 thoughts on “CodeIT repository: RPM and DEB packages of NGINX, Apache httpd with HTTP/3 and OpenSSL for RHEL and Ubuntu”

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

2. Guys,
   Love the Builds. Great Work
   Love from India

   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

4. Hello,

   Just asking is the repos are safe.. I am seeing codeit along with the installed packages

   Reply

   1. Hello Arun,

      You use this repository as is at your own risk.

      Reply

      1. Hello Alexander,

         Thanks for your reply.

         I am going to do the source code compilation method.

         Reply

5. Very good work, thank you very much!

   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

   1. Hello Frank,

      Sorry, we do not provide support for Virtualmin. If you believe this flavour is easy to support, you can use our source RPMs and add a simple patch for your own builds.

      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

   1. This is the default page. Please simply add index.html to your document root.

      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

   1. Hello,

      We are running smoothly.
      I read the error description and see that you have file write problem to your disk.
      Please run this from root user.

      Reply

      1. Don’t I feel foolish. 🙂

         Reply

10. Can you please add mod_fcgid as a RPM to your Apache repo?

    https://httpd.apache.org/mod_fcgid/

    Reply

    1. Added, please test.

       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. Please install EPEL repo, we require it for all the dependencies.

       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

13. Thank you Alexander for your great work and support.

    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

17. Looking for ETA for openssl3.0 support with apache.
    Openssl1.1.1 will reach EOL by the end of Sep 2023.

    Reply

    1. Thanks for pointing out!
       We definitely plan to stay with 100% supported software and will move to OpenSSL 3 before the 1.1.1 EOL.

       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

          1. Great it works! EL9 patching added to the CI/CD pipelines.

             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!

24. Hello and thank you for your help.

    I have recenty tried to update httpd but recieved the folloing forbidden error:

    failure: repodata/repomd.xml from CodeIT: [Errno 256] No more mirrors to try.
    https://repo.codeit.guru/packages/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 – Forbidden

    How can I correct this.

    Thank you!

    Joe

    Reply

    1. Hello Joe,

       CentOS 7 reached its EOL. Please read
       https://codeit.guru/2024/07/centos-7-eol/

       Reply

       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

          1. Yes, exactly, $5+ recurring donation, PayPal is usually cheaper by fees, ip(s) via dm.

             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

          1. Also as I mentioned other IPs from the same /24 network block don’t have such issues.

             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

          1. Thanks, I whitelisted it. More details sent by email

             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

    1. Hello Kenny,
       https://codeit.guru/en_US/2024/07/centos-7-eol/

       Reply

27. Can be added also the rtmp module for nginx in the repo?

    Reply

    1. Hello,

       For now, we do not have plans to add 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. Hi Emilio,

       https://codeit.guru/2024/07/centos-7-eol/

       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

    1. Sure, all the chances. Could you provide exact steps to reproduce the problem?

       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. This looks like CentOS Stream that has its own build of OpenSSL 3.5.5. We unfortunately do not support CentOS Stream now (only RHEL and its clones).

       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

    2. This also should be fixed with the suffixed OpenSSL 4.0.0 as libcrypto.so.81.4 and libssl.81.4
       Please test

       Reply

33. You guys have always been awesome! Currently I’m unable to reach your repos for Centos7:

    https://repo.codeit.guru/packages/mainline/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 – Forbidden

    And in fact can’t even reach the centos7 packages URL here:
    https://repo.codeit.guru/packages/mainline/centos/7/

    Any issues on your end?

    Reply

    1. Hi Nate, thank you.
       After eol, CentOS 7 is subscription only, as it is much more pain and effort to patch and keep builds, build new compilers stack
       https://codeit.guru/2024/07/centos-7-eol/

       Reply

34. We would like to know an ETA on updating the apr-util to resolve the below vulnerability
    https://cvefeed.io/vuln/detail/CVE-2026-34501

    Reply

    1. Nanda, thank you for pointing out, will put it today to testing and probably released tomorrow if tests are green

       Reply

    2. Released, thanks again for pointing out – missed apr-util upstream feed.

       Reply

35. Hi Alexander,

    I’d like to ask whether it’s possible to integrate the ProxyWebsocketIdleTimeout directive (mod_proxy_wstunnel module) into your Apache 2.4 package.

    RHEL and derivatives (RHEL 8 through 9, CentOS, AlmaLinux) carry this as a maintained, self-contained patch on top of upstream.

    The same implementation has been carried forward from their 2.4.37 base up to current 2.4.62-based builds (most recently tracked as RHEL-53722). It’s independent of the ProxyWebsocketAsync machinery that exists in trunk, so it applies cleanly to a stock 2.4 tree without extra dependencies.

    The problem it solves: without it, WebSocket tunnels proxied through mod_proxy_wstunnel either stay open indefinitely while idle or get closed prematurely depending on generic timeout settings, causing WebSocket connections to drop unpredictably behind the reverse proxy.

    Reference patch: httpd-2.4.37-proxy-ws-idle-timeout.patch in the CentOS/RHEL httpd RPM sources (git.centos.org/rpms/httpd).

    Let me know if you need anything else to evaluate it.

    Thanks.

    Reply

    1. Hi Alessio,

       I will review and integrate it. Probably it looks like a simple solution for 2.4.69+.

       Thank you for pointing out it is already included in rhel. We always tried to build an in-place replacement for stock web servers that does not break any current set ups.

       Reply

    2. Alessio, I tested the patch – it’s more problematic for fresh builds than it looked.
       With RHEL’s patch exactly as shipped, a vhost that configures the directive gets an immediate timeout – the tunnel never opens:
       main-server -> HTTP 101 vhost -> HTTP 000

       I fed it to AI to get the root cause and I see that patch no more lands on 2.4.68 and needs rework. Fedora no more ships it.
       Details below:

       [proxy_wstunnel:error] (70007)The timeout specified has expired:
       [client 127.0.0.1:37488] RH: the connection has timed out

       Cause: putting any wstunnel directive in the vhost creates the vhost’s own proxyws_dir_conf, so merge_proxyws_dir_config runs — and RHEL’s patch never taught the merge about idle_timeout. apr_pcalloc leaves it 0, and apr_pollset_poll(pollset, 0, …) returns APR_TIMEUP at once. The vhost’s configured 300 is discarded too, so in vhost scope the directive doesn’t work at all. RHEL 9 and 10 ship this defect; it hides because it needs ProxyWebsocketFallbackToProxyHttp Off.

       Fedora:
       %bcond wstunnel %[0%{?fedora} < 45 && 0%{?rhel} < 11] # for F45+ remove mod_proxy_wstunnel, deprecated upstream since 2.4.47 Fedora is dropping mod_proxy_wstunnel for F45+/RHEL11+ — upstream deprecated it in 2.4.47 in favour of mod_proxy_http handling the upgrade, where ProxyTimeout already covers the idle case

       Reply

       1. Alexander,

          Thanks for digging into this, makes sense now.

          According to your findings, I don’t think it’s worth chasing a fix.

          I’ll run extensive tests on httpd >= 2.4.68, making sure ProxyWebsocketFallbackToProxyHttp is explicitly On (or confirmed On by default) so mod_proxy_http takes over the tunnel lifecycle, and drop ProxyWebsocketIdleTimeout entirely in favor of ProxyTimeout.

          Thank you for your effort.

          Reply

36. Does mod_http3 still require these directives:

    H3CertificatePath
    H3CertificateKeyPath ?

    I find this cumbersome, Ai says it is not needed but the official documentation says it is required.

    I want it to use standard path for existing cert.

    Reply

    1. Hi Luca, these directives are hard requirements, and there is no fallback to mod_ssl. You can’t drop the directives, but you can stop repeating files – just point it to the same paths or use variables.
       This is unfortunately original author’s decision and the module is in active development at the moment. I only updated and patched httpd for testing and getting early feedback.
       Feel free to post it to the original machine-moon github repo.

       Reply