Unable to see webhooks #2592
Comments
|
Allright, after diggin a bit into it i could get the following errors. This is what i get from the chrome developer-console: And this is what i can see from the docker-compose logs: Not sure if this could be an reverse-proxy config. I've been playing around a bit with it, so here is the config (with some out commented lines) <VirtualHost *:80>
ServerName docs.fuchscloud.de
ProxyPreserveHost On
ProxyPass / http://192.168.127.232:7880/
ProxyPassReverse / http://192.168.127.232:7880/
RewriteEngine on
# RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
RewriteCond %{SERVER_NAME} =docs.fuchscloud.de
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>
<IfModule mod_ssl.c>
<VirtualHost *:443>
ServerName docs.fuchscloud.de
ProxyPreserveHost On
#ProxyPass /api/v1/sec/ws ws://192.168.127.232:7880/api/v1/sec/ws
#ProxyPassReverse /api/v1/sec/ws ws://192.168.127.232:7880/api/v1/sec/ws
#ProxyPass /(.*) http://192.168.127.232:7880/$1
ProxyPass / http://192.168.127.232:7880/
#ProxyPassReverse /(.*) http://192.168.127.232:7880/$1
ProxyPassReverse / http://192.168.127.232:7880/
RewriteEngine on
RewriteCond %{SERVER_NAME} =docs.fuchscloud.de
# RewriteRule ^ http://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
# RewriteRule /api/v1/sec/ws ws://192.168.127.232:7880/api/v1/sec/ws [P,L]
Include /etc/apache2/sites-enabled/local-network.config
Include /etc/apache2/ssl-options.conf
</VirtualHost> |
|
Hi @mikedolx oh that doesn't look nice. For some reason you have a notification hook without a "channel". I think it would be good to check the table |
|
Hi @eikek , thanks für the reply. It took me some time, to get pgadmin attached to the db, but here i am now. Please find below a screenshot of my
EDIT: To answer your question: I don't actually know how i get into this state. I just created one webhook after another. As they did not show up in the ui i thought, that something must be wrong, so i created another one. This issue persists a bit longer, as you can see by the creation date of the hooks. |
|
I'm sorry, I'd need another table :) The table you showed is the main one and you can see the first row is the hook that is in a bad state (it's id is mentioned in the exception in the logs). If you don't hang on to it too strongly you can just delete that row. Then the error won't appear anymore. For the cause, there is another table, connecting channels to a hook. So that one hook can use multiple channels to send its messages (gotify, matrix etc). This table is The message bombardment is probably caused by too many hooks triggered for the same event. If you like to start from scratch, you can empty the table |
Hi,
I was playing around with webhooks and set up some notification forwarding.
After some time I realized, that there are no webhooks visible in the docspell-ui. I remember clicking on the save button multiple times.
Now, when I edit a document/item I get four notifications. I guess, I had set up four webhooks, but can't see any of those.
Any idea, how I can either delete all webhooks, or make them visible again?
I'm running in the latest docspell 0.41.0 on docker-compose.
Any hints appreciated.
The text was updated successfully, but these errors were encountered: