From 80a225c677ed5252b4cc69a1182e280a8e88fe20 Mon Sep 17 00:00:00 2001 From: Pierre <66693681+extua@users.noreply.github.com> Date: Tue, 8 Jul 2025 01:16:12 +0100 Subject: [PATCH] docs(deployment): add note about potential firewall issues on RHEL (#2707) Add a warning box to the troubleshooting advice (https://docs.browsertrix.com/deploy/local/#debugging-pod-issues) in the local deployment guide about firewall rules and disabling firewalld on RHEL. See https://forum.webrecorder.net/t/browsertrix-deployment-stalls-when-initializing-container-migrations/916/5 for context. --- frontend/docs/docs/deploy/local.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/frontend/docs/docs/deploy/local.md b/frontend/docs/docs/deploy/local.md index f49f6b1c..3f371599 100644 --- a/frontend/docs/docs/deploy/local.md +++ b/frontend/docs/docs/deploy/local.md @@ -180,11 +180,16 @@ There should be 4 pods listed: backend, frontend, minio, and mongodb. If any one To get more details about why a pod has not started, run `#!sh kubectl describe ` and see the latest status at the bottom. -Often, the error may be obvious, such as failed to pull an image. +Often, the error may be obvious, such as "failed to pull an image." -If the pod is running, or previously ran, you can also get the logs from the container by running `#!sh kubectl logs ` +If the pod is running, or previously ran, you can also get the logs from the container by running `#!sh kubectl logs `. -The outputs of these commands are helpful when reporting an issue [on GitHub](https://github.com/webrecorder/browsertrix/issues) +The outputs of these commands are helpful when reporting an issue [on GitHub](https://github.com/webrecorder/browsertrix/issues). + +??? info "Firewall rules (on RHEL/Fedora)" + + On Red Hat Enterprise Linux and derivatives, communication between pods might be blocked by firewalld. + There are short guides on configuring the firewall for these systems in the [k3s](https://docs.k3s.io/installation/requirements?&os=rhel#operating-systems) and [Microk8s](https://microk8s.io/docs/troubleshooting#:~:text=Pod%20communication%20problems%20when%20using%20firewall-cmd) documentation. ## Updating the Cluster