Closed DrTableBasse closed 16 hours ago
Try reset the UI:
I just tried right now and nothing change lol x)
Latest logs :
main-1 | Creating group siyuan (1000)
main-1 | Creating user siyuan (PUID: 1000, PGID: 1000)
main-1 | Adjusting ownership of /opt/siyuan, /home/siyuan/, and /siyuan/workspace/
main-1 | Starting Siyuan with UID:1000 and GID:1000 in workspace /siyuan/workspace/
main-1 | I 2024/12/03 14:55:20 working.go:147:
main-1 | ___ ___ ___ ___
main-1 | / /\ ___ ___ /__/\ / /\ /__/\
main-1 | / /:/_ / /\ /__/| \ \:\ / /::\ \ \:\
main-1 | / /:/ /\ / /:/ | |:| \ \:\ / /:/\:\ \ \:\
main-1 | / /:/ /::\ /__/::\ | |:| ___ \ \:\ / /:/~/::\ _____\__\:\
main-1 | /__/:/ /:/\:\ \__\/\:\__ __|__|:| /__/\ \__\:\ /__/:/ /:/\:\ /__/::::::::\
main-1 | \ \:\/:/~/:/ \ \:\/\ /__/::::\ \ \:\ / /:/ \ \:\/:/__\/ \ \:\~~\~~\/
main-1 | \ \::/ /:/ \__\::/ ~\~~\:\ \ \:\ /:/ \ \::/ \ \:\ ~~~
main-1 | \__\/ /:/ /__/:/ \ \:\ \ \:\/:/ \ \:\ \ \:\
main-1 | /__/:/ \__\/ \__\/ \ \::/ \ \:\ \ \:\
main-1 | \__\/ \__\/ \__\/ \__\/
main-1 | I 2024/12/03 14:55:20 runtime.go:87: kernel is booting:
main-1 | * ver [3.1.14]
main-1 | * arch [amd64]
main-1 | * os [alpine]
main-1 | * pid [1]
main-1 | * runtime mode [prod]
main-1 | * working directory [/opt/siyuan]
main-1 | * read only [false]
main-1 | * container [docker]
main-1 | * database [ver=20220501]
main-1 | * workspace directory [/siyuan/workspace/]
main-1 | I 2024/12/03 14:55:20 conf.go:130: loaded conf [/siyuan/workspace/conf/conf.json]
main-1 | I 2024/12/03 14:55:20 runtime.go:139: use network proxy [system]
main-1 | I 2024/12/03 14:55:20 serve.go:209: kernel [pid=1] http server [0.0.0.0:6806] is booting
main-1 | I 2024/12/03 14:55:20 conf.go:851: database size [3.8 MB], tree/block count [20/1459]
main-1 | I 2024/12/03 14:55:20 working.go:193: kernel booted
main-1 | I 2024/12/03 14:55:20 box.go:77: auto stat [trees=20, blocks=1459, dataSize=54.8 MB, assetsSize=54.26 MB]
main-1 | W 2024/12/03 14:55:20 serve.go:589: closed an unauthenticated session [172.20.0.3:53542]
main-1 | 2024/12/03 14:55:20 http: response.Write on hijacked connection from github.com/gin-gonic/gin.(*responseWriter).Write (response_writer.go:83)
main-1 | W 2024/12/03 14:55:22 serve.go:589: closed an unauthenticated session [172.20.0.3:53554]
main-1 | 2024/12/03 14:55:22 http: response.Write on hijacked connection from github.com/gin-gonic/gin.(*responseWriter).Write (response_writer.go:83)
main-1 | W 2024/12/03 14:55:23 serve.go:589: closed an unauthenticated session [172.20.0.3:53560]
main-1 | 2024/12/03 14:55:23 http: response.Write on hijacked connection from github.com/gin-gonic/gin.(*responseWriter).Write (response_writer.go:83)
main-1 | W 2024/12/03 14:55:23 serve.go:589: closed an unauthenticated session [172.20.0.3:53572]
main-1 | 2024/12/03 14:55:23 http: response.Write on hijacked connection from github.com/gin-gonic/gin.(*responseWriter).Write (response_writer.go:83)
main-1 | I 2024/12/03 14:55:46 session.go:121: auth success [ip=172.20.0.3:37834]
main-1 | 2024/12/03 14:55:46 http: response.Write on hijacked connection from github.com/gin-gonic/gin.(*responseWriter).Write (response_writer.go:83)
main-1 | 2024/12/03 14:56:02 http: response.Write on hijacked connection from github.com/gin-gonic/gin.(*responseWriter).Write (response_writer.go:83)
main-1 | 2024/12/03 14:56:02 http: response.Write on hijacked connection from github.com/gin-gonic/gin.(*responseWriter).Write (response_writer.go:83)
To give more informations, I have authentik in front to create authentification for my users and have Nginx Proxy manager in front too
NPM ---> Authentik ---> Siyuan
So basically i never had problem with siyuan, but i think with the latest, it should create some problems
It seems to be a problem with access authorization. I guess you can only check it yourself.
OK so I check with older version it works ! So If u want, i'll keep this issue open and check in parallele with newest version
This is probably not SiYuan's issue. I closed it. Thanks for the feedback.
It's Siyuan issue...
Please remove the middleware from the test to avoid the impact of the environment configuration.
I already do that lol and have the same problem
I can screenshot again if you want 😄
Do you mean there will be authentication issues if you access the IP:port directly?
I disable authentik SSO I try directly with ip:port directly for siyuan and got the same problem Any pages doesn't want load as the screen I sended
Please send a new log.
the logs are the same as i send before... :-/
main-1 | W 2024/12/03 14:55:22 serve.go:589: closed an unauthenticated session [172.20.0.3:53554]
Check your WebSocket proxy configuration
Yeah i check it and it's OK For me, it's the new version which as problem as i said before x) maybe it's fault about which data i have idk
We have not received similar feedback from other users so far. We recommend that you check your configuration and environment.
Is there an existing issue for this?
Can the issue be reproduced with the default theme (daylight/midnight)?
Could the issue be due to extensions?
Describe the problem
When I want to load any page, I dont have any results. I delete all plugin, restart the container and have the same problem..
Expected result
Just want to read article for my team x)
Screenshot or screen recording presentation
Version environment
Log file
I 2024/12/03 14:17:24 runtime.go:87: kernel is booting:
More information
No response