Skip to content

[stable32] fix: proxy route leading slash #3465

[stable32] fix: proxy route leading slash

[stable32] fix: proxy route leading slash #3465

Triggered via pull request May 15, 2026 14:12
Status Success
Total duration 16m 8s
Artifacts 26

tests-deploy.yml

on: pull_request
NC In Host
1m 37s
NC In Host
NC In Julius Docker
2m 47s
NC In Julius Docker
NC In Julius Docker(DSP-HTTP)
1m 42s
NC In Julius Docker(DSP-HTTP)
NC In Julius Docker(DSP-HTTPS)
1m 48s
NC In Julius Docker(DSP-HTTPS)
NC In Host(Redis)
1m 57s
NC In Host(Redis)
NC In Host(network=host)
1m 41s
NC In Host(network=host)
NC In Julius Docker (HaRP-Bridge network)
1m 49s
NC In Julius Docker (HaRP-Bridge network)
NC In Julius Docker (HaRP-Bridge network-no FRP TLS)
1m 55s
NC In Julius Docker (HaRP-Bridge network-no FRP TLS)
NC In Host (HaRP-Host network)
2m 6s
NC In Host (HaRP-Host network)
NC In Host (Manual HaRP-Host network)
6m 50s
NC In Host (Manual HaRP-Host network)
NC In Julius Docker(DSP-HTTPS-BRIDGE)
1m 58s
NC In Julius Docker(DSP-HTTPS-BRIDGE)
NC In Host(Redis) Deploy options
2m 3s
NC In Host(Redis) Deploy options
Tests-Deploy-OK
3s
Tests-Deploy-OK
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
NC In Host(Redis)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@ec406be512d7077f68eed36e63f4d91bc006edc4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Julius Docker(DSP-HTTP)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Host
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@ec406be512d7077f68eed36e63f4d91bc006edc4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Host(network=host)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@ec406be512d7077f68eed36e63f4d91bc006edc4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Julius Docker
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Host (HaRP-Host network)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@ec406be512d7077f68eed36e63f4d91bc006edc4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Julius Docker(DSP-HTTPS)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Host(Redis) Deploy options
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@ec406be512d7077f68eed36e63f4d91bc006edc4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Julius Docker(DSP-HTTPS-BRIDGE)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Host (Manual HaRP-Host network)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@ec406be512d7077f68eed36e63f4d91bc006edc4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
dsp_http_container.json
3.27 KB
sha256:da5d6879d1b188163fbc7cc1e18fed7ad05da5824c4bb6594fabc4ed465a3dc2
dsp_http_container.log
935 Bytes
sha256:d204b08d46dc914eb338fcde610f3c7fe6a163e27a8d8cdf255506e16da344f2
dsp_http_nextcloud.log
597 Bytes
sha256:7f78f1df00156b5a67376f20fc29ea319ae8f6187884fcad1d03940d7102eb5a
dsp_https_bridge_container.json
3.35 KB
sha256:4d5c2c2c54a80cc7af735f202ce06ba9af72ba145b369e9b8e3cc3dfa3a55ed0
dsp_https_bridge_container.log
934 Bytes
sha256:77669a1ba1643097c52def8cfc418519dbab208281ef17ba1495e98761d7cf18
dsp_https_bridge_haproxy.log
3.64 KB
sha256:aba46d6415f913c4e081fa328b61272fa87d03fc39906c95fbe69b14d609c51a
dsp_https_bridge_nextcloud.log
600 Bytes
sha256:02d10ad324920ec272715d90e80e1d2c927d26201bd0e5b5d7f6f7268c679e40
dsp_https_container.json
3.24 KB
sha256:cde03c04f9b60a32489827318306e0219f0d8feb5e689a41a236d81d36bbc580
dsp_https_container.log
928 Bytes
sha256:a43b856138380f6bed29d6759a86a72869408eb2c08da5f4feb39fa1932c3aae
dsp_https_haproxy.log
3.58 KB
sha256:7e552984e0123c561616561a68f5946fbecb2bd80f46d29d00f17a6ce0249343
dsp_https_nextcloud.log
601 Bytes
sha256:7d13e120b3b083dad23f147ec074dc4153831b1d8b815f3a57aa7166c82a3883
nc_docker_app_docker_container.json
147 Bytes
sha256:ae47f22c38d90281b5a1bb512b105383bdcc1a8961bacd80986ec747575e79ba
nc_docker_app_docker_container.log
944 Bytes
sha256:0d7fa1dcbd479ef06c932805872499a8504791139014f6daaab8dc1c3d502616
nc_docker_app_docker_nextcloud.log
596 Bytes
sha256:04c753c0fdec584618b17422f7e436c9ec847f872861edfde9efd8008ba03fd1
nc_host_app_docker_container.json
3.22 KB
sha256:4e8d26b08181327f75a4ed7d848ad32d24ac11b48a604ec3cf24a10dbecc2020
nc_host_app_docker_container.log
940 Bytes
sha256:7d343048286098ff3c4507a513ee1f33eca5438389ff763d1d6a471030273b31
nc_host_app_docker_nextcloud.log
31.1 KB
sha256:baa14caac1b2c26437ecbb2a2a985e5fbf59979a460d3f619f10a3884b3b1f76
nc_host_app_docker_redis_container.json
3.22 KB
sha256:33aec70ff9f61c4e6e4d531ca2b6e628537a9ab650c0de4f2f7add7c65415df3
nc_host_app_docker_redis_container.log
932 Bytes
sha256:193da86fdccab806adfdfaf4b90f0cacb61d76acc80c855b2e5e63205e795259
nc_host_app_docker_redis_deploy_options_container.json
3.29 KB
sha256:1528915320251f84bd85c51e944178dba76d6c293ed70797c1ef4687bef1d512
nc_host_app_docker_redis_deploy_options_container.log
939 Bytes
sha256:9190a35988032ab24b21e85e697c658dc32d2b64ada29bf62819a51614d77c9c
nc_host_app_docker_redis_deploy_options_nextcloud.log
31.1 KB
sha256:45af42e92d7df0675339a41b3a2b4d128de6c697c98cbe1123cc2eb6840fd64c
nc_host_app_docker_redis_nextcloud.log
34.8 KB
sha256:8d20694cafe548369e71421c8002988c8f4838bad68f6dd5ef6759f57012b580
nc_host_network_host_container.json
3.22 KB
sha256:b1e3dc4a615818e4760527db6b9586a4f10699196a400719599d257533f59393
nc_host_network_host_container.log
936 Bytes
sha256:d6dbe95d3ed2c5f1bcc4ba25f0166ae23f00ea5462fb6b7773eaf880d06b8265
nc_host_network_host_nextcloud.log
31.5 KB
sha256:e3cc3511f3808d7f8903c11ac61ea96eecd5c3676d9f1a6d6a7b99b01f59d8cc