Originally created by @davaded on GitHub (Apr 25, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Git Clone
Open WebUI Version
v0.6.5
Ollama Version (if applicable)
no
Operating System
cent os7
Browser (if applicable)
Chrome
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 listed steps to reproduce the bug in detail.
Expected Behavior
There was no problem after changing the database to PostgreSQL, but
I kept getting this error when I restarted today and couldn't enter the container again
peewee.IntegrityError: could not create unique index "tag_id"
DETAIL: Key (id)=(history) is duplicated.
Actual Behavior
peewee.IntegrityError: could not create unique index "tag_id"
DETAIL: Key (id)=(history) is duplicated.
Steps to Reproduce
There was no problem after changing the database to PostgreSQL, but
I kept getting this error when I restarted today and couldn't enter the container again
Logs & Screenshots
There was no problem after changing the database to PostgreSQL, but
I kept getting this error when I restarted today and couldn't enter the container again
peewee.IntegrityError: could not create unique index "tag_id"
DETAIL: Key (id)=(history) is duplicated.
Additional Information
No response
Originally created by @davaded on GitHub (Apr 25, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Git Clone
### Open WebUI Version
v0.6.5
### Ollama Version (if applicable)
no
### Operating System
cent os7
### Browser (if applicable)
Chrome
### 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 listed steps to reproduce the bug in detail.
### Expected Behavior
There was no problem after changing the database to PostgreSQL, but
I kept getting this error when I restarted today and couldn't enter the container again
``` bash
peewee.IntegrityError: could not create unique index "tag_id"
DETAIL: Key (id)=(history) is duplicated.
```

### Actual Behavior
``` bash
peewee.IntegrityError: could not create unique index "tag_id"
DETAIL: Key (id)=(history) is duplicated.
```
### Steps to Reproduce
There was no problem after changing the database to PostgreSQL, but
I kept getting this error when I restarted today and couldn't enter the container again
### Logs & Screenshots
There was no problem after changing the database to PostgreSQL, but
I kept getting this error when I restarted today and couldn't enter the container again
``` bash
peewee.IntegrityError: could not create unique index "tag_id"
DETAIL: Key (id)=(history) is duplicated.
```

### Additional Information
_No response_
GiteaMirror
added the bug label 2025-11-11 16:08:08 -06:00
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 @davaded on GitHub (Apr 25, 2025).
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
v0.6.5
Ollama Version (if applicable)
no
Operating System
cent os7
Browser (if applicable)
Chrome
Confirmation
README.md.Expected Behavior
There was no problem after changing the database to PostgreSQL, but
I kept getting this error when I restarted today and couldn't enter the container again
Actual Behavior
Steps to Reproduce
There was no problem after changing the database to PostgreSQL, but
I kept getting this error when I restarted today and couldn't enter the container again
Logs & Screenshots
There was no problem after changing the database to PostgreSQL, but
I kept getting this error when I restarted today and couldn't enter the container again
Additional Information
No response