I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Other
Open WebUI Version
v0.6.18
Ollama Version (if applicable)
No response
Operating System
OpenShift 4.18
Browser (if applicable)
No response
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
Expected Behavior
After the pod restarts, connections to the model remain.
Actual Behavior
Loss of connections to models after pod restart
Steps to Reproduce
Deploy OpenWebUI on OpenShift using PVC.
Login to OpenWebUI.
Go Admin Panel -> Settings -> Connections
Add new connection
Restart pod
After logging in again, the added connection disappears.
Originally created by @pbartczak on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16179
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Other
### Open WebUI Version
v0.6.18
### Ollama Version (if applicable)
_No response_
### Operating System
OpenShift 4.18
### Browser (if applicable)
_No response_
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
After the pod restarts, connections to the model remain.
### Actual Behavior
Loss of connections to models after pod restart
### Steps to Reproduce
1. Deploy OpenWebUI on OpenShift using PVC.
2. Login to OpenWebUI.
3. Go Admin Panel -> Settings -> Connections
4. Add new connection
5. Restart pod
6. After logging in again, the added connection disappears.
### Logs & Screenshots
Deployment:
`kind: Deployment
apiVersion: apps/v1
metadata:
name: open-webui
namespace: open-webui
spec:
replicas: 1
selector:
matchLabels:
app: open-webui
template:
metadata:
creationTimestamp: null
labels:
app: open-webui
spec:
restartPolicy: Always
serviceAccountName: open-webui
schedulerName: default-scheduler
terminationGracePeriodSeconds: 30
securityContext: {}
containers:
- resources:
limits:
cpu: '1'
memory: 1Gi
requests:
cpu: 500m
memory: 500Mi
terminationMessagePath: /dev/termination-log
name: open-webui
env:
- name: ENABLE_OLLAMA_API
value: 'False'
- name: OPENAI_API_BASE_URL
value: 'https://bielik-bielik/v1'
- name: OPENAI_API_KEY
valueFrom:
secretKeyRef:
name: openai-api-key
key: api-key
- name: GLOBAL_LOG_LEVEL
value: DEBUG
- name: REQUESTS_CA_BUNDLE
value: /var/secrets/ca-bundle.crt
- name: SSL_CERT_FILE
value: /var/secrets/ca-bundle.crt
- name: ENABLE_OAUTH_GROUP_MANAGEMENT
value: 'true'
ports:
- containerPort: 8080
protocol: TCP
imagePullPolicy: IfNotPresent
volumeMounts:
- name: webui-volume
mountPath: /app/backend/data
- name: certs-volume
readOnly: true
mountPath: /var/secrets
terminationMessagePolicy: File
envFrom:
- secretRef:
name: configuration
- secretRef:
name: ldap-integration
tty: true
image: 'open-webui:main'
serviceAccount: open-webui
volumes:
- name: webui-volume
persistentVolumeClaim:
claimName: open-webui-pvc
- name: certs-volume
secret:
secretName: ca-certs
defaultMode: 420
dnsPolicy: ClusterFirst
strategy:
type: RollingUpdate
rollingUpdate:
maxUnavailable: 25%
maxSurge: 25%
revisionHistoryLimit: 10
progressDeadlineSeconds: 600`
Configuration secret env:
` DEFAULT_USER_ROLE: user
ENABLE_PERSISTENT_CONFIG: false
ENABLE_SIGNUP: false
OFFLINE_MODE: true
USER_PERMISSIONS_WORKSPACE_MODELS_ACCESS: true`
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-04-19 23:42:31 -05:00
Please read the docs, ENABLE_PERSISTENT_CONFIG will reset your config entry from the db.
<!-- gh-comment-id:3139586459 -->
@tjbck commented on GitHub (Jul 31, 2025):
Please read the docs, `ENABLE_PERSISTENT_CONFIG` will reset your config entry from the db.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @pbartczak on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16179
Check Existing Issues
Installation Method
Other
Open WebUI Version
v0.6.18
Ollama Version (if applicable)
No response
Operating System
OpenShift 4.18
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
After the pod restarts, connections to the model remain.
Actual Behavior
Loss of connections to models after pod restart
Steps to Reproduce
Logs & Screenshots
Deployment:
kind: Deployment apiVersion: apps/v1 metadata: name: open-webui namespace: open-webui spec: replicas: 1 selector: matchLabels: app: open-webui template: metadata: creationTimestamp: null labels: app: open-webui spec: restartPolicy: Always serviceAccountName: open-webui schedulerName: default-scheduler terminationGracePeriodSeconds: 30 securityContext: {} containers: - resources: limits: cpu: '1' memory: 1Gi requests: cpu: 500m memory: 500Mi terminationMessagePath: /dev/termination-log name: open-webui env: - name: ENABLE_OLLAMA_API value: 'False' - name: OPENAI_API_BASE_URL value: 'https://bielik-bielik/v1' - name: OPENAI_API_KEY valueFrom: secretKeyRef: name: openai-api-key key: api-key - name: GLOBAL_LOG_LEVEL value: DEBUG - name: REQUESTS_CA_BUNDLE value: /var/secrets/ca-bundle.crt - name: SSL_CERT_FILE value: /var/secrets/ca-bundle.crt - name: ENABLE_OAUTH_GROUP_MANAGEMENT value: 'true' ports: - containerPort: 8080 protocol: TCP imagePullPolicy: IfNotPresent volumeMounts: - name: webui-volume mountPath: /app/backend/data - name: certs-volume readOnly: true mountPath: /var/secrets terminationMessagePolicy: File envFrom: - secretRef: name: configuration - secretRef: name: ldap-integration tty: true image: 'open-webui:main' serviceAccount: open-webui volumes: - name: webui-volume persistentVolumeClaim: claimName: open-webui-pvc - name: certs-volume secret: secretName: ca-certs defaultMode: 420 dnsPolicy: ClusterFirst strategy: type: RollingUpdate rollingUpdate: maxUnavailable: 25% maxSurge: 25% revisionHistoryLimit: 10 progressDeadlineSeconds: 600Configuration secret env:
DEFAULT_USER_ROLE: user ENABLE_PERSISTENT_CONFIG: false ENABLE_SIGNUP: false OFFLINE_MODE: true USER_PERMISSIONS_WORKSPACE_MODELS_ACCESS: trueAdditional Information
No response
@tjbck commented on GitHub (Jul 31, 2025):
Please read the docs,
ENABLE_PERSISTENT_CONFIGwill reset your config entry from the db.