# Error with code blocks: 403 Forbidden
**URL:** https://meta.discourse.org/t/error-with-code-blocks-403-forbidden/280764
**Category:** Support
**Created:** [October 2, 2023, 4:12pm UTC](https://meta.discourse.org/t/error-with-code-blocks-403-forbidden/280764 "2023-10-02T16:12:13Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@gkaf89](https://meta.discourse.org/u/gkaf89)
#### Post date: [October 2, 2023, 4:12pm UTC](https://meta.discourse.org/t/error-with-code-blocks-403-forbidden/280764/1 "2023-10-02T16:12:13Z")
I recently took on the management of discourse server, and there are a few issues.
1. I have persistent issues when trying to create or edit a post with code blocks. When trying to create or edit a post with the code block
```plaintext
(access node)$ spack list openfoam@2306
...
Variants:
Name [Default] When Allowed values Description
====================== ==== ============== ==================================================
build_system [generic] -- generic Build systems supported by the package
int64 [off] -- on, off With 64-bit labels
kahip [off] -- on, off With kahip decomposition
knl [off] -- on, off Use KNL compiler settings
metis [off] -- on, off With metis decomposition
mgridgen [off] -- on, off With mgridgen support
paraview [off] -- on, off Build paraview plugins and runtime post-processing
precision [dp] -- sp, dp, spdp Precision option
scotch [on] -- on, off With scotch/ptscotch decomposition
source [on] -- on, off Install library/application sources and tutorials
vtk [off] -- on, off With VTK runTimePostProcessing
zoltan [off] -- on, off With zoltan renumbering
...
```
I get an error `403 Forbidden`.
1. Markdown does not support code highlighting adding any syntax specification results in an error `403 Forbidden`.
2. Inline code segments also cause `403 Forbidden` in some but not all locations, relative to other code blocks.
The installed version is 3.1.1 ( [0612f0d5b6](https://github.com/discourse/discourse/commits/0612f0d5b60708cadffc8b7ebad1419eda96f60b) ).
Are these issues related, and what could be causing this behavior?
_Example post:_ [Compiling OpenFOAM with Spack - π Knowledge nuggets - HPC discourse](https://hpc-discourse.uni.lu/t/compiling-openfoam-with-spack/109)
# Intended result:
There are some issues when installing OpenFOAM of OpenCFD with Spack.
An environment was set up to manage the packages with Spack following the instruction in the UL HPC tutorial. In short, the following dependencies where defined for the SPACK packages,
```bash
(access node)$ cat << EOF >> $SPACK_ROOT/etc/spack/packages.yaml
packages:
slurm:
externals:
- spec: slurm@22.05.5
prefix: /usr
buildable: False
libevent:
externals:
- spec: libevent@2.1.8
prefix: /usr
buildable: False
pmix:
externals:
- spec: pmix@4.2.3
prefix: /usr
buildable: False
hwloc:
externals:
- spec: hwloc@2.2.0
prefix: /usr
buildable: False
EOF
```
and the following options were defined for the build cache directories,
```bash
(access)$ cat << EOF >> $SPACK_ROOT/etc/spack/config.yaml
config:
build_stage:
- /dev/shm/$user/spack-stage
EOF
```
to speed-up compilation using the ramdisk file system. Before proceeding to the installation of OpenFOAM the desired version of Open MPI is installed with the system compiler:
```bash
(compute node)$ spack install -j openmpi@4.0.5 +pmi schedulers=slurm ^pmix@4.2.3 ^hwloc@2.2.0
```
The distribution of OpenFOAM is installed using the system compiler as well. The available components of OpenFOAM are:
```plaintext
(access node)$ spack list openfoam@2306
...
Variants:
Name [Default] When Allowed values Description
====================== ==== ============== ==================================================
build_system [generic] -- generic Build systems supported by the package
int64 [off] -- on, off With 64-bit labels
kahip [off] -- on, off With kahip decomposition
knl [off] -- on, off Use KNL compiler settings
metis [off] -- on, off With metis decomposition
mgridgen [off] -- on, off With mgridgen support
paraview [off] -- on, off Build paraview plugins and runtime post-processing
precision [dp] -- sp, dp, spdp Precision option
scotch [on] -- on, off With scotch/ptscotch decomposition
source [on] -- on, off Install library/application sources and tutorials
vtk [off] -- on, off With VTK runTimePostProcessing
zoltan [off] -- on, off With zoltan renumbering
...
```
OpenFOAM is installed using all the available partitioners (`metis`, `scotch`, `zoltan`, `kahip`) and the multi-grid generator components (`mgridgen`, section 6.3.1.4 of the documentation) with the command:
```bash
(compute node)$ spack install -j openfoam@2306 +source precision=dp +metis +scotch +zoltan +kahip +mgridgen ~knl ~int64 ~paraview ^openmpi@4.0.5
```
However, the resulting installation is missing multiple components. For instance, executing the manual post installation verification in `doc/Build.md`,
```bash
# Create the user "run" directory:
mkdir -p "$FOAM_RUN"
# Change to the user "run" directory:
run
# Copy tutorial
cp -r "$FOAM_TUTORIALS"/incompressible/simpleFoam/pitzDaily ./
# Run the tutorial
( cd pitzDaily && blockMesh && simpleFoam )
```
both the mesh generator `blockMesh` and the solver `simpleFoam` are missing.
It turns out that the METIS partitioner causes the installation of multiple components to fail. Recompiling with only the SCOTCH partitioner,
```bash
(compute node)$ spack install openfoam@2306 +source +scotch +mgridgen precision=dp ~int64 ~kahip ~knl ~metis ~paraview ~vtk ~zoltan ^openmpi@4.0.5
```
solves the issue. All solver components are installed, but a few utilities are still missing.
We use the following script to detect all missing components:
```bash
(access node)$ cat list_spack_openfoam
#!/usr/bin/bash
set -euo pipefail
declare variant="${1}" # e.g. @2306%gcc@8.5.0 @2306+mgridgen
declare type="${2}" # solvers, utilities
find_makefile_directories() {
local directory="${1}"
find "${directory}" -type d | grep -E '\/Make$' || true
}
extract_executable_name() {
local makefile_directory="${1}"
cat "${makefile_directory}/files" | ( grep -E '^EXE[[:space:]]*=' || true ) | sed 's/^EXE[[:space:]]*=[[:space:]]*\$(FOAM_APPBIN)\///g'
}
main() {
local variant="${1}"
local type="${2}"
local foam_location="$(spack location -i openfoam"${variant}")"
local pagkage_directory=""
local executable_name=""
local installed=""
local package_makefile_directory=""
while read -r package_makefile_directory; do
executable_name=$( extract_executable_name "${package_makefile_directory}" )
if [-n "${executable_name}"]; then
if [-x "${foam_location}/platforms/linux64GccDPInt32-spack/bin/${executable_name}"]; then
installed="Y"
else
installed="N"
fi
package_directory="$( echo "${package_makefile_directory}" | xargs -I % dirname % )"
echo "${installed} : ${executable_name} => ${package_directory#${foam_location}}"
fi
done < <( find_makefile_directories "${foam_location}/applications/${type}" )
}
main "${variant}" "${type}"
```
A simple run of the script indicates that the following utilities are missing:
```plaintext
(access node)$ ./list_spack_openfoam utilities @2306 | grep -E '^N'
N : addr2line => /applications/utilities/miscellaneous/OSspecific/addr2line
N : foamyHexMeshSurfaceSimplify => /applications/utilities/mesh/generation/foamyMesh/foamyHexMeshSurfaceSimplify
N : foamyHexMeshBackgroundMesh => /applications/utilities/mesh/generation/foamyMesh/foamyHexMeshBackgroundMesh
N : cellSizeAndAlignmentGrid => /applications/utilities/mesh/generation/foamyMesh/cellSizeAndAlignmentGrid
N : foamToCcm => /applications/utilities/mesh/conversion/ccm/foamToCcm
N : ccmToFoam => /applications/utilities/mesh/conversion/ccm/ccmToFoam
```
---
### Author:  [@nat](https://meta.discourse.org/u/nat)
#### Post date: [October 2, 2023, 5:03pm UTC](https://meta.discourse.org/t/error-with-code-blocks-403-forbidden/280764/2 "2023-10-02T17:03:52Z")
Itβs hard to tell, Markdown-related issues tend to not be 403s but have some UI feedback to the author. Our 403 errors tend to be related to authorisation, like posting in a category that is restricted, or using a restricted tag.
I used your text chunks in a vanilla instance of Discourse and it seems to be fine.
Could I suggest you check with [your moderator](https://hpc-discourse.uni.lu/t/about-the-knowledge-nuggets-category/37) to see if such restrictions are in place?
---
### Author:  [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [October 2, 2023, 5:09pm UTC](https://meta.discourse.org/t/error-with-code-blocks-403-forbidden/280764/3 "2023-10-02T17:09:02Z")
> [@nat](#):
>
> Could I suggest you check with [your moderator](https://hpc-discourse.uni.lu/t/about-the-knowledge-nuggets-category/37) to see if such restrictions are in place?
Further to this, we nearly _always_ find that 403 errors like this when attempting to create posts (especially with code blocks!) are due to an overzealous [WAF](https://en.wikipedia.org/wiki/Web_application_firewall) believing the code blocks are shellcode or an injection attack.
I note that the instance in question seems to be fronted by a WAF:
```plaintext
β β host hpc-discourse.uni.lu
hpc-discourse.uni.lu is an alias for fstc-waf2.uni.lu.
```
and thus I strongly suspect the 403 errors are coming not from Discourse, but from your WAF.
Inspecting the headers of the errors in the browser should be able to tell you the source of the rejection.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [November 1, 2023, 5:09pm UTC](https://meta.discourse.org/t/error-with-code-blocks-403-forbidden/280764/4 "2023-11-01T17:09:24Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.