\n\n### Expected behavior\n\n```\ndocker run --rm --privileged \\\n -v $(pwd):/woodpecker \\\n -e PLUGIN_REPO=demo/myap \\\n -e PLUGIN_TAGS=latest \\\n -e PLUGIN_PLATFORMS=linux/amd64 \\\n -e PLUGIN_DOCKERFILE=Dockerfile \\\n -e PLUGIN_DRIVER=docker \\\n -e PLUGIN_BUILDKIT_DRIVEROPT=\"image=moby/buildkit:master\" \\\n -w /woodpecker \\\n woodpeckerci/plugin-docker-buildx:5.2.2-insecure\n```\n\n\u003Cimg width=\"2083\" height=\"456\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/763aa4cd-edc1-4e07-b043-44b5d153d962\" />\n\n### System Info\n\n```shell\ndocker desktop v4.43.1\n```\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [x] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/versions]",[3054],{"name":3035,"color":3036},5321,"plugin-docker-buildx insecure with PLUGIN_BUILDKIT_DRIVEROPT image not work after version 6","2025-07-14T03:09:06Z","https://github.com/woodpecker-ci/woodpecker/issues/5321",0.7626752,{"description":3061,"labels":3062,"number":3067,"owner":3024,"repository":3025,"state":3026,"title":3068,"updated_at":3069,"url":3070,"score":3071},"### Component\n\nserver\n\n### Describe the bug\n\nWhen transferring a repo from a user to another in Gitea/Forgejo, the repo disappears from the sender's Woodpecker, but when trying to enable it from the receiver's Woodpecker it says it already is active.\r\n\r\n\r\n\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"1.0.0\"}\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[3063,3064],{"name":3035,"color":3036},{"name":3065,"color":3066},"server","5D7A92",2109,"[gitea] transferring a repo breaks it","2023-08-03T22:54:39Z","https://github.com/woodpecker-ci/woodpecker/issues/2109",0.7632456,{"description":3073,"labels":3074,"number":3082,"owner":3024,"repository":3025,"state":3083,"title":3084,"updated_at":3085,"url":3086,"score":3087},"\r\n\r\nif you open the menue to show running builds, the log view and so the download-button does not move as expected",[3075,3076,3079],{"name":3035,"color":3036},{"name":3077,"color":3078},"ui","46DEA2",{"name":3080,"color":3081},"ux","fef2c0",1137,"closed","[UI] log-download button glitch ","2022-09-01T18:35:37Z","https://github.com/woodpecker-ci/woodpecker/issues/1137",0.65857345,{"description":3089,"labels":3090,"number":3093,"owner":3024,"repository":3025,"state":3083,"title":3094,"updated_at":3095,"url":3096,"score":3097},"### Component\n\nweb-ui\n\n### Describe the bug\n\nOn output with 5500 lines, clicking pipeline which is producing these lines in realtime browser gets frozen with message \"Woodpecker is not reposinding [WAIT]\". After build is done and we reopen woodpecker in different tab we able to see an output.\n\n### System Info\n\n```shell\n0.15.32\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy).",[3091,3092],{"name":3035,"color":3036},{"name":3077,"color":3078},768,"Browser tab crashes when long output printed and we attempt to monitor it in real time","2022-06-16T17:24:28Z","https://github.com/woodpecker-ci/woodpecker/issues/768",0.73772687,{"description":3099,"labels":3100,"number":3102,"owner":3024,"repository":3025,"state":3083,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Component\n\nserver\n\n### Describe the bug\n\nI cannot login to Woodpecker in the latest version.\r\nI use Gitea as my git service.\r\nWhen I click on login I see a quick flash of the dashboard and it then returns to the login page.\r\nSee the logs below.\r\n\r\nI have tested earlier versions of the server to see when this started failing.\r\nLast working version is next-9c684b7a22.\r\n\n\n### System Info\n\n```shell\nnext-fbdfa14a00\n```\n\n\n### Additional context\n\n```\r\n2:44PM INF woodpecker/src/github.com/woodpecker-ci/woodpecker/cmd/server/server.go:268 > starting Woodpecker server with version 'next-fbdfa14a00'\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/grpc/rpc.go:56 > agent connected: vault: polling\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/grpc/rpc.go:56 > agent connected: devbox: polling\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip= latency=0.064702 method=GET path=/version status=200 user-agent=\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36\"\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip= latency=0.049213 method=GET path=/favicon.ico status=200 user-agent=\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36\"\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip= latency=0.05822 method=GET path=/ status=200 user-agent=\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36\"\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip= latency=0.295395 method=GET path=/web-config.js status=200 user-agent=\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36\"\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip= latency=0.268325 method=GET path=/assets/custom.css status=200 user-agent=\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36\"\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip= latency=0.050325 method=GET path=/assets/custom.js status=200 user-agent=\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36\"\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/api/stream.go:63 > user feed: connection opened\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip= latency=0.072135 method=GET path=/login status=303 user-agent=\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36\"\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip= latency=0.094808 method=GET path=/authorize status=303 user-agent=\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36\"\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip= latency=0.047449 method=GET path=/login/oauth/authorize status=200 user-agent=\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36\"\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip= latency=0.048372 method=GET path=/assets/custom.css status=200 user-agent=\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36\"\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip= latency=0.152978 method=GET path=/web-config.js status=200 user-agent=\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36\"\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip= latency=0.052358 method=GET path=/assets/custom.js status=200 user-agent=\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36\"\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/api/stream.go:63 > user feed: connection opened\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip=::1 latency=0.211017 method=GET path=/healthz status=204 user-agent=Go-http-client/1.1\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/api/stream.go:82 > user feed: connection closed\r\n2:44PM DBG woodpecker/src/github.com/woodpecker-ci/woodpecker/server/router/middleware/logger.go:59 > ip= latency=8292.925219 method=GET path=/api/stream/events status=200 user-agent=\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36\"\r\n```\n\n### Validations\n\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]",[3101],{"name":3035,"color":3036},3531,"Can't login to Woodpecker in latest version.","2024-03-21T18:18:24Z","https://github.com/woodpecker-ci/woodpecker/issues/3531",0.73863536,{"description":3108,"labels":3109,"number":3111,"owner":3024,"repository":3025,"state":3083,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nWith the `2.7.1` -> `2.7.2` upgrade, woodpecker always returns a blank page. It seems to be trying to redirect to the `/login?url=/repos` page, but returns a blank page\r\n\r\n### Steps to reproduce\r\n\r\n1. Have a working 2.7.1 install\r\n2. Upgrade to 2.7.2\r\n3. All pages are blank, and the loging redirect fails.\r\n\r\n### Expected behavior\r\n\r\nIt should correctly handle login redirects\r\n\r\n### System Info\r\n\r\n```shell\r\n`\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.7.2\"}`\r\n```\r\n\r\nLuckily there were no migrations as far as I can tell, so switching back to the `v2.7.1` docker tag seems to be working fine.\r\n\r\n### Additional context\r\n\r\nNA\r\n\r\n### Validations\r\n\r\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\r\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\r\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]",[3110],{"name":3035,"color":3036},4294,"Woodpecker `2.7.2` broke login auth redirects, always returns blank page.","2024-11-06T17:32:33Z","https://github.com/woodpecker-ci/woodpecker/issues/4294",0.74497557,{"description":3117,"labels":3118,"number":3121,"owner":3024,"repository":3025,"state":3083,"title":3122,"updated_at":3123,"url":3124,"score":3125},"### Component\n\nserver, web-ui\n\n### Describe the bug\n\nOne of my new repositories was not showing up in the repository list.\r\nI clicked 'Synchronise' in the web UI and there was a notification telling me that it was successful.\r\nMy new repository did not show up. I didn't see anything in Woodpecker's logs and I spent a long time looking through the code to figure it out.\r\nEventually I looked through the Gitea logs and saw that the request failed with a 401 Unauthorised error.\r\n\r\nIf I recall, logging out through the web UI and then logging in again caused the synchronise button to work again.\r\n\r\n(There might be a separate issue here about Gitea access tokens expiring or something? But ideally a Gitea API error should not show up as successful. Oops!)\r\n\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"${VERSION}\"}\r\n```\r\n... hmm.\r\n\r\nI'm using the `florianpiesche/woodpecker-server:v0.14.1` Docker image on a RPi 4.\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy).",[3119,3120],{"name":3035,"color":3036},{"name":3077,"color":3078},503,"'Successfully synchronized your repository list' even though Gitea's logs show 401 Unauthorised","2021-11-26T03:02:03Z","https://github.com/woodpecker-ci/woodpecker/issues/503",0.745702,["Reactive",3127],{},["Set"],["ShallowReactive",3130],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f-Tf8shUABOzEmhyz-iSkqYEPI4Og0gmEAK2GNjLiexw":-1},"/woodpecker-ci/woodpecker/3825"]