403 Forbidden Error with conda.software.inl.gov/public - Cloudflare Bot Protection Blocking Conda Access #31919

arndflatten · 2025-11-14T08:50:44Z

arndflatten
Nov 14, 2025

Check these boxes if you have followed the posting rules.

I have consulted the Posting Guidelines.
I have searched the Discussions Forum and MOOSE Framework Troubleshooting and have not found what I was looking for
Q&A Getting Started is the most appropriate category for my question (trouble installing, beginner user, ...)

Issue or question about MOOSE

I am unable to access the MOOSE conda channel at https://conda.software.inl.gov/public when using conda commands, despite the channel being accessible via web browser. This appears to be caused by Cloudflare bot protection blocking programmatic access.

Is this a known/recent change? Has Cloudflare bot protection been recently enabled or strengthened on conda.software.inl.gov?
Is there a workaround?

Could the MOOSE/INL team please investigate the Cloudflare configuration for conda.software.inl.gov to allow legitimate conda client access? The current bot protection appears to be blocking all programmatic access, which breaks the conda package distribution system. Any guidance on workarounds or timeline for a fix would be greatly appreciated.

Thank you for any assistance!

more information, that might be useful below:

Environment Details

Operating System: Linux (RHEL 8.7, kernel 4.18.0-425.13.1.el8_7.x86_64)
Conda Version: 25.9.1
Python Version: 3.12.7
Conda Installation: Miniforge3 at /home/moose/miniforge
Solver: libmamba (default)

Channel Configuration

$ conda config --show channels
channels:
  - https://conda.software.inl.gov/public
  - conda-forge

Symptoms

Web Browser Access: ✓ WORKS When accessing https://conda.software.inl.gov/public in a web browser, the channel is fully accessible and shows the package listing.
Conda Commands: ✗ FAILS Any conda command attempting to access the channel fails with HTTP 403:

$ conda env update --name moose --file conda_env_moose.yaml

Channels:
 - conda-forge
 - https://conda.software.inl.gov/public
Platform: linux-64
Collecting package metadata (repodata.json): ...working... failed

UnavailableInvalidChannel: HTTP 403 Forbidden for channel public <https://conda.software.inl.gov/public>

The channel is not accessible or is invalid.

You will need to adjust your conda configuration to proceed.
Use `conda config --show channels` to view your configuration's current state,
and use `conda config --show-sources` to view config file locations.

Direct Testing:

$ conda search moose --channel https://conda.software.inl.gov/public --override-channels
Loading channels: failed

UnavailableInvalidChannel: HTTP 403 Forbidden for channel public <https://conda.software.inl.gov/public>

Root Cause Analysis

Using curl to inspect the HTTP response headers reveals that Cloudflare is blocking the requests:

$ curl -I https://conda.software.inl.gov/public/linux-64/repodata.json

HTTP/2 403
content-type: text/html; charset=UTF-8
cf-mitigated: challenge

The cf-mitigated: challenge header indicates that Cloudflare is presenting a JavaScript challenge page (the "Just a moment..." page), which conda/Python's requests library cannot solve because it requires JavaScript execution and cookie handling. Why Browser Works but Conda Doesn't:
Web browsers can execute JavaScript to solve Cloudflare's bot detection challenge
Conda uses Python's requests library, which cannot execute JavaScript
The server returns an HTML challenge page instead of the requested JSON data

Additional Testing

Testing with different user agents shows that all programmatic access is blocked, not just conda:

# Using conda's user-agent
$ curl -H "User-Agent: conda/25.9.1 requests/2.32.5 CPython/3.12.7 Linux/4.18.0" \
  https://conda.software.inl.gov/public/channeldata.json
<!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title>...

# Using browser user-agent - also blocked
$ curl -H "User-Agent: Mozilla/5.0" https://conda.software.inl.gov/public/channeldata.json
<!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title>...

# Python requests library - also blocked
$ python -c "import requests; r = requests.get('https://conda.software.inl.gov/public/channeldata.json'); print(r.status_code)"
403

as additional info

System Configuration Files

My conda_env_moose.yaml includes standard MOOSE packages:

name: moose
channels:
  - conda-forge
  - https://conda.software.inl.gov/public
dependencies:
  - moose-dev=2025.09.04=mpich
  - moose-libmesh=2025.08.06=mpich_0
  - moose-tools=2025.06.26=py313h831f05b_0
  # ... [other dependencies]

Attempted Workarounds (None Successful)

✗ Verified channel URL is correct (/public suffix included)
✗ Tested with different user agents
✗ Confirmed SSL verification settings
✗ Checked proxy/firewall settings (none configured)
✗ Attempted with both conda and mamba
✗ Tested from different shell sessions

(Optional) code in question / simulation log / errors

No response

Encountering Errors? Please include diagnostic output

####################################################################################################
Influential Environment Variables

CONDA_CHANNEL=https://conda.software.inl.gov/public
CONDA_DEFAULT_ENV=moose
CONDA_EXE=/home/moose/miniforge/bin/conda
CONDA_PREFIX_1=/home/moose/miniforge
CONDA_PREFIX_2=/home/moose/miniforge/envs/moose
CONDA_PREFIX_3=/home/moose/miniforge
CONDA_PREFIX=/home/moose/miniforge/envs/moose
CONDA_PROMPT_MODIFIER=(moose) 
CONDA_PYTHON_EXE=/home/moose/miniforge/bin/python
CONDA_SHLVL=4
CURL_CA_BUNDLE=
MOOSE_JOBS=6
PATH=/home/moose/miniforge/envs/moose/bin:/home/moose/miniforge/bin:/home/moose/.vscode-server/cli/servers/Stable-7d842fb85a0275a4a8e4d7e040d2625abbf7f084/server/bin/remote-cli:/home/moose/miniforge/bin:/home/moose/miniforge/bin:/home/moose/miniforge/condabin:/home/moose/.local/bin:/home/moose/bin:/home/moose/miniforge/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/abaqus/Commands:/var/DassaultSystemes/SIMULIA/Commands:/usr/abaqus/Commands:/var/DassaultSystemes/SIMULIA/Commands:/usr/abaqus/Commands:/var/DassaultSystemes/SIMULIA/Commands:/usr/abaqus/Commands:/var/DassaultSystemes/SIMULIA/Commands
REQUESTS_CA_BUNDLE=
SSL_CERT_FILE=/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
####################################################################################################
Compiler(s) (CC CXX FC F77 F90):

CC      not set
CXX     not set
FC      not set
F77     not set
F90     not set

FAIL: One or more compiler environment variables not set, or set incorrectly
####################################################################################################
Python Sanity Checks

/usr/bin/env python3 --version; (reporting as: Python 3.12.7) matches
which python3 python;

/home/moose/miniforge/bin/python3 --version; == Python 3.12.7
/home/moose/miniforge/bin/python --version; == Python 3.12.7

OK
####################################################################################################
Python Modules (TestHarness, run-ability)


WARNING: missing module(s): pyaml jinja2 

Either install the above packages, or perhaps you have yet
to activate the moose environment: conda activate moose

Missing 'warning' Python modules may cause miscellaneous runtime issues.

WARNING: One or more Python issues present.
####################################################################################################
MOOSE Repository/Conda Version Checks

WARNING: Unable to run Conda tests due to missing Python modules


checks FAILED

Answered by loganharbour

Nov 17, 2025

We've setup the proper exclusions for conda.software.inl.gov. Workarounds should no longer be needed.

View full answer

kmkim3182 · 2025-11-14T15:44:48Z

kmkim3182
Nov 14, 2025

Not only is updating failing, but the initial installation also fails in my case. The same error (403: invalid channel) occurs.

4 replies

kmkim3182 Nov 14, 2025

#28577

Same thing in 2024. Guess it's a nationality issue.

GiudGiud Nov 14, 2025
Collaborator

no it's not

It's an ongoing cloudflare -related disruption

GiudGiud Nov 14, 2025
Collaborator

it will be resolved momentarily by INL cyber team

PengWei97 Nov 15, 2025

Hi @GiudGiud, I also have encountered the same problem, just like this:

(base) pw-moose@pwmoose-PowerEdge-T640:                                                                                                                                                 
~                                                                                                                                                                                       
$ conda create -n moose moose-dev=2025.10.27=mpich                                                                                                                                      
Channels:                                                                                                                                                                               
 - https://conda.software.inl.gov/public                                                                                                                                                
 - conda-forge                                                                                                                                                                          
Platform: linux-64                                                                                                                                                                      
Collecting package metadata (repodata.json): failed

UnavailableInvalidChannel: HTTP 403 Forbidden for channel public <https://conda.software.inl.gov/public>

The channel is not accessible or is invalid.

You will need to adjust your conda configuration to proceed.
Use `conda config --show channels` to view your configuration's current state,
and use `conda config --show-sources` to view config file locations.

and I look forward to further news from you.

Wei

arndflatten · 2025-11-17T09:48:14Z

arndflatten
Nov 17, 2025
Author

There is a potential workaround to avoid using the Conda-INL_channel, =if= you have an explicit package list saved

conda config --remove channels https://conda.software.inl.gov/public
conda install --name moose --file conda_env_moose_explicit.txt --yes --quiet

However, you need to have this explicit list saved first.

For example, on a working conda environment you could

conda activate moose  # the working env
conda list --explicit > conda_env_moose_explicit.txt

to create such a file, or the moose-developers decide to host such a comprehensive list (if applicable, what do you think @GiudGiud)?

2 replies

GiudGiud Nov 17, 2025
Collaborator

Can you download the packages manually too from your browser ?

ansvbayer Nov 17, 2025

Can you please give an example of the package list?
I haven't installed moose yet, still struggling.

loganharbour · 2025-11-17T16:21:41Z

loganharbour
Nov 17, 2025
Maintainer

We've setup the proper exclusions for conda.software.inl.gov. Workarounds should no longer be needed.

3 replies

aswin-polyenergetics · 2026-02-11T14:36:14Z

aswin-polyenergetics
Feb 11, 2026

@loganharbour @GiudGiud I'm getting a 502 error for the channel: https://conda.software.inl.gov/public

From browser:

Logs when trying to setup the conda environment:

(base) ubuntu@ip-xxx-xx-xx-xx:~$ conda config --add channels https://conda.software.inl.gov/public
(base) ubuntu@ip-xxx-xx-xx-xx:~$ conda create -n moose moose
Channels:
 - https://conda.software.inl.gov/public
 - conda-forge
Platform: linux-64
Collecting package metadata (repodata.json): failed

CondaHTTPError: HTTP 502 Bad Gateway for url <https://conda.software.inl.gov/public/linux-64/repodata.json>
Elapsed: 00:01.084970
CF-RAY: 9cc45e48dc2c2cc2-DFW

A remote server error occurred when trying to retrieve this URL.

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
fulfill a valid request.  The problem may be spurious, and will resolve itself if you
try your request again.  If the problem persists, consider notifying the maintainer
of the remote server.

(I have commented the same in another issue that seemed related: #28885)

2 replies

loganharbour Feb 11, 2026
Maintainer

@aswin-polyenergetics - our servers were down overnight for updates. It should be good now. Please try again.

aswin-polyenergetics Feb 11, 2026

It is loading fine now - Thank you @loganharbour !

403 Forbidden Error with conda.software.inl.gov/public - Cloudflare Bot Protection Blocking Conda Access #31919

Uh oh!

Check these boxes if you have followed the posting rules.

Issue or question about MOOSE

Environment Details

Channel Configuration

Symptoms

Root Cause Analysis

Additional Testing

as additional info

System Configuration Files

Attempted Workarounds (None Successful)

(Optional) code in question / simulation log / errors

Encountering Errors? Please include diagnostic output

Replies: 4 comments · 11 replies

Uh oh!

Uh oh!

Uh oh!

GiudGiud Nov 14, 2025 Collaborator

Uh oh!

GiudGiud Nov 14, 2025 Collaborator

Uh oh!

Uh oh!

Uh oh!

arndflatten Nov 17, 2025 Author

Uh oh!

GiudGiud Nov 17, 2025 Collaborator

Uh oh!

Uh oh!

loganharbour Nov 17, 2025 Maintainer

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

loganharbour Feb 11, 2026 Maintainer

Uh oh!

Replies: 4 comments 11 replies

GiudGiud Nov 14, 2025
Collaborator

GiudGiud Nov 14, 2025
Collaborator

arndflatten
Nov 17, 2025
Author

GiudGiud Nov 17, 2025
Collaborator

loganharbour
Nov 17, 2025
Maintainer

loganharbour Feb 11, 2026
Maintainer