微信云托管官网
最新提问- 全部
- 文章
- 问答
- 全部
- 文章
- 问答
置顶云托管-云端调试-云调用-报错 47001 data format error？
微信小程序团队你好， 使用 Python在云托管尝试调用微信 API短信发送 data = { "env": 'xxx', "content": '哎哟嘿', "path": '/index.html', "phoneNumberList": ["+8613812345678"], "smsType": "Marketing", "useShortName": True } url = 'http://api.weixin.qq.com/tcb/sendsms' resp = requests.post(url, data=json.dumps(data, ensure_ascii=False).encode('utf-8')) 实际 requests 的 data 为 b'{"env": "xxx", "content": "\xe5\x93\x8e\xe5\x93\x9f\xe5\x98\xbf", "path": "/index.html", "phoneNumberList": ["+8613812345678"], "smsType": "Marketing", "useShortName": true}' 但是报错 200 OK Content-Length: 78 Content-Type: application/json Date: Sun, 21 Jul 2024 22:05:30 GMT Server: Tencent-CloudBase X-Cloudbase-Request-Id: 58204170-47ad-11ef-846c-525400a903d3 X-Cloudbase-Upstream-Status-Code: 200 X-Cloudbase-Upstream-Timecost: 242 X-Cloudbase-Upstream-Type: Tencent-CBR X-Request-Id: 58204170-47ad-11ef-846c-525400a903d3 X-Upstream-Status-Code: 200 X-Upstream-Timecost: 242 { errcode:47001 errmsg:"data format error rid: 669d862a-18bd6106-7587fc42" } x 已经在 云托管-云调用-微信令牌权限增加了 '/tcb/sendsms'测试是在云托管-云端调试进行的HTTP 已经使用 utf-8 对中文 content 编码了env 填写了配置的云开发环境 id, 在小程序内云调用函数没问题，短信也成功扣除。就是在云托管测试出错。 请问具体问题是什么？谢谢！
07-22置顶云托管-已经设置项目组，为何组员进入又要新建和创建实例，才能进入到管理台？
云托管已经部署spring boot应用，为什么环境管理者进入控制台要先部署才能进入到下图的管理界面 [图片]
07-20置顶【云托管问题】如果我不保底一个实例的话，这样经常会遇到别人无法访问服务器。
https://developers.weixin.qq.com/minigame/dev/wxcloudrun/src/Billing/example.html [图片] 如果实例设置为0，那这样虽然是按需扣费，但是服务器每次都要等有人访问才启动，这样会导致有些人没办法使用。。 而如果设置实例为1，那这样又很贵，24小时都在扣钱。请问这要怎么办？
07-19置顶请问一下云托管部署服务后是计量收费吗，如何看到产生的费用呢？
请问一下云托管部署后端服务服务后的计量收费细节是什么呢，如何看到产生的费用呢？
07-18置顶在微信云托管中，如何获取对象存储临时密钥？
// 在服务启动时或者页面加载时初始化，注意这是异步的，需要等待完成，可以通过 this.cos 是否存在来判断是否完成。 initcos() /** * 封装的COS-SDK初始化函数，建议在服务启动时挂载全局，通过this.cos使用对象 */ async function initcos() { try { const res = await fetch('https://api.weixin.qq.com/_/cos/getauth', { method: 'GET' }) console.log('res',res); } catch (e) { console.log('COS初始化失败', e) } } [图片] [图片]
07-15置顶小程序云部署微信支付无法授权?
[图片]
07-15置顶腾讯云主机，能访问微信云托管上的mysql吗？
前期我们是基于微信云托管开发的小程序，现在相应的app开发出来了，使用了腾讯云上的自建服务，想共享同一地区微信云托管上mysql中的数据，可以直接通过数据库内网ip连接云托管上的mysql吗？有没有什么限制？
07-15置顶本地调试时，自动创建的服务 wxcloud-localdebug-proxy 扣费吗？
vscode 本地调试时，自动创建的服务 wxcloud-localdebug-proxy 扣费吗？
07-09置顶小程序云托管模式付费能否用腾讯云的账号？
我要开发一个小程序，用云托管模式来支付小程序运行所需的云资源。请问下这个是否能和我的腾讯云账号绑定，用我腾讯云账号里的费用来支付小程序的云托管费用。
07-08置顶小程序云托管模式付费问题
我要开发一个小程序，用云托管模式来支付小程序运行所需的云资源。请问下这个是否能和我的腾讯云账号绑定，用我腾讯云账号里的费用来支付小程序的云托管费用。
07-08置顶【新手】云托管的数据库访问处理官方有没有提供可用库？还是需要使用者按需自己实现？
例如，我用sequelize 库处理数据 ？
07-06理解有误；参考了官方的服务模板，koa的示例代码。里面同样使用了 sequelize库 处理数据~
有同样问题的同学，可以参考官方服务模板 https://github.com/WeixinCloud/wxcloudrun-koa/tree/main
自己改改，或者按照技能经验 自行处理。
--------------------------------
刚刚翻看社区文章，看到微信提供了这个sdk，@cloudbase/node-sdk https://developers.weixin.qq.com/community/develop/article/doc/0000e2a4cccbe8b2695bed5d256c13
我觉得，这个可以在官方文档 微信云托管-MYSQL 章节添加以下~ 新手开局直接使用云托管，需要面临如何处理托管数据库的业务数据处理问题，希望官方考虑一下~
有用 10置顶云托管里面的对象储存如何自定义域名？
你好，请问各位云托管里面的对象储存如何自定义域名？我只知道服务里面可以自定义域名，还有静态资源部署里面可以，但是我没看到对象储存里面在哪里可以自定义域名？
07-06置顶云端调试Websocket接口如何处理1006错误码？
在云端调试托管服务的Websocket接口时，经测试，若超出一分钟未有内容传输，则Websocket连接则会自动断开，并返回1006错误码。本地启动该服务则不会出现该情况。 请问微信针对Websocket接口是否有隐含的心跳检测？用户能否自己配置超时时间？或者倘若想要保持长链接，有何其他建议方案？ [图片]
07-04置顶云托管开通了服务，但是小程序服务器域名配那块没有自动跟上！怎么联起来？
[图片]
07-03置顶端口无误，配置未改，日志显示SUCCESS，无Error。部署却显示失败？
部署日志如下： [2024-06-30 23:57:08] 0eea81b8f3e9: Layer already exists [2024-06-30 23:57:08] 0a6f98eeb095: Layer already exists [2024-06-30 23:57:08] 3999ea91fb6e: Layer already exists [2024-06-30 23:57:08] 43df359389fd: Layer already exists [2024-06-30 23:57:08] d3e8d42f967c: Layer already exists [2024-06-30 23:57:08] 5d64de483bf5: Layer already exists [2024-06-30 23:57:09] 9a1c92c2d99a: Pushed [2024-06-30 23:57:09] 50371b0f5b94: Pushed [2024-06-30 23:57:10] 65727e6ebea8: Pushed [2024-06-30 23:57:10] 37b30ca5d103: Pushed [2024-06-30 23:59:31] 093fc442b171: Pushed [2024-06-30 23:59:31] niji-api-server-031-20240630235040: digest: sha256:4c121e42559558ec29765ef0e64b4dc6630686badd4aa65997422f0a862cebfd size: 3053 [2024-06-30 23:59:31] [Pipeline] } [2024-06-30 23:59:31] [Pipeline] // stage [2024-06-30 23:59:31] [Pipeline] } [2024-06-30 23:59:31] [Pipeline] // node [2024-06-30 23:59:31] [Pipeline] End of Pipeline [2024-06-30 23:59:31] Finished: SUCCESS *** -----------构建niji-api-server-031----------- 2024-06-30 23:50:42 create_build_image : succ, 2024-06-30 23:59:33 check_build_image : succ, , -----------服务niji-api-server部署niji-api-server-031----------- 2024-06-30 23:59:34 create_eks_virtual_service : succ, 2024-06-30 23:59:34 check_eks_virtual_service : process, DescribeVersion_not_ready, 明晃晃的看到了SUCCESS。但却说我部署失败。 运行日志里面没有错误。本地运行正常。前些天部署正常。 为什么部署不成功。想不明白。
07-01置顶同一规模的应用，是用云托管搭建，还是自行去腾讯云上购买组装更划算？
同等规模的应用，包括app/小程序共用一套后端服务，是用云托管搭建，还是自行去腾讯云上购买更划算？
06-28置顶微信云托管新建flask服务失败怎么办？
部署开始于 2024-06-28 15:50:16 AppID: wxc46331858565a277 环境名称：prod-9g7nsxtpd55ed7d6 [1/2] 创建版本 失败 228s 创建版本失败：任务失败 [2024-06-28 15:50:24] Started by user coding [2024-06-28 15:50:24] Running in Durability level: MAX_SURVIVABILITY [2024-06-28 15:50:26] [Pipeline] Start of Pipeline [2024-06-28 15:50:26] [Pipeline] node [2024-06-28 15:50:26] Running on Jenkins in /root/workspace [2024-06-28 15:50:26] [Pipeline] { [2024-06-28 15:50:26] [Pipeline] stage [2024-06-28 15:50:26] [Pipeline] { (检出 ZIP 包) [2024-06-28 15:50:26] [Pipeline] sh [2024-06-28 15:50:26] + curl -L -u ****** -o code.zip [2024-06-28 15:50:26] % Total % Received % Xferd Average Speed Time Time Time Current [2024-06-28 15:50:26] Dload Upload Total Spent Left Speed [2024-06-28 15:50:27] 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 9790 100 9790 0 0 37780 0 --:--:-- --:--:-- --:--:-- 37653 [2024-06-28 15:50:27] [Pipeline] sh [2024-06-28 15:50:27] + unzip code.zip [2024-06-28 15:50:27] Archive: code.zip [2024-06-28 15:50:27] inflating: Dockerfile [2024-06-28 15:50:27] inflating: requirements.txt [2024-06-28 15:50:27] creating: app/ [2024-06-28 15:50:27] inflating: app/config.py [2024-06-28 15:50:27] inflating: app/fpxz.py [2024-06-28 15:50:27] [Pipeline] } [2024-06-28 15:50:27] [Pipeline] // stage [2024-06-28 15:50:27] [Pipeline] stage [2024-06-28 15:50:27] [Pipeline] { (检出代码仓库) [2024-06-28 15:50:27] Stage "检出代码仓库" skipped due to when conditional [2024-06-28 15:50:27] [Pipeline] } [2024-06-28 15:50:27] [Pipeline] // stage [2024-06-28 15:50:27] [Pipeline] stage [2024-06-28 15:50:27] [Pipeline] { (构建 Docker 镜像) [2024-06-28 15:50:27] [Pipeline] sh [2024-06-28 15:50:28] + docker login -u ****** -p ****** ccr.ccs.tencentyun.com/tcb-******-hljm/ca-bugxylvt_fpxz:fpxz-006-20240628155022 [2024-06-28 15:50:28] WARNING! Using --password via the CLI is insecure. Use --password-stdin. [2024-06-28 15:50:28] WARNING! Your password will be stored unencrypted in /root/.docker/config.json. [2024-06-28 15:50:28] Configure a credential helper to remove this warning. See [2024-06-28 15:50:28] https://docs.docker.com/engine/reference/commandline/login/#credentials-store [2024-06-28 15:50:28] [2024-06-28 15:50:28] Login Succeeded [2024-06-28 15:50:28] [Pipeline] sh [2024-06-28 15:50:28] + docker build -f ././/Dockerfile -t ccr.ccs.tencentyun.com/tcb-******-hljm/ca-bugxylvt_fpxz:fpxz-006-20240628155022 ./ [2024-06-28 15:50:28] DEPRECATED: The legacy builder is deprecated and will be removed in a future release. [2024-06-28 15:50:28] Install the buildx component to build images with BuildKit: [2024-06-28 15:50:28] https://docs.docker.com/go/buildx/ [2024-06-28 15:50:28] [2024-06-28 15:50:28] Sending build context to Docker daemon 87.55kB [2024-06-28 15:50:28] Step 1/11 : FROM python:3.9-slim [2024-06-28 15:50:29] 3.9-slim: Pulling from library/python [2024-06-28 15:50:29] 2cc3ae149d28: Pulling fs layer [2024-06-28 15:50:29] 670483cd5170: Pulling fs layer [2024-06-28 15:50:29] 8b920a4a2006: Pulling fs layer [2024-06-28 15:50:29] 48e2a65c587f: Pulling fs layer [2024-06-28 15:50:29] d95408d27250: Pulling fs layer [2024-06-28 15:50:29] 48e2a65c587f: Download complete [2024-06-28 15:50:30] d95408d27250: Verifying Checksum [2024-06-28 15:50:30] 670483cd5170: Verifying Checksum [2024-06-28 15:50:30] 670483cd5170: Download complete [2024-06-28 15:50:30] 8b920a4a2006: Verifying Checksum [2024-06-28 15:50:30] 8b920a4a2006: Download complete [2024-06-28 15:50:32] 2cc3ae149d28: Verifying Checksum [2024-06-28 15:50:32] 2cc3ae149d28: Download complete [2024-06-28 15:50:33] 2cc3ae149d28: Pull complete [2024-06-28 15:50:33] 670483cd5170: Pull complete [2024-06-28 15:50:34] 8b920a4a2006: Pull complete [2024-06-28 15:50:34] 48e2a65c587f: Pull complete [2024-06-28 15:50:34] d95408d27250: Pull complete [2024-06-28 15:50:34] Digest: sha256:d3185e5aa645a4ff0b52416af05c8465d93791e49c5a0d0f565c119099f26cde [2024-06-28 15:50:34] Status: Downloaded newer image for python:3.9-slim [2024-06-28 15:50:34] ---> 04bf3d9a322b [2024-06-28 15:50:34] Step 2/11 : RUN python -m venv /env [2024-06-28 15:50:34] ---> Running in 3bd017616df3 [2024-06-28 15:50:41] Removing intermediate container 3bd017616df3 [2024-06-28 15:50:41] ---> a9ce996e123f [2024-06-28 15:50:41] Step 3/11 : ENV PATH="/env/bin:$PATH" [2024-06-28 15:50:41] ---> Running in be4380e940d7 [2024-06-28 15:50:41] Removing intermediate container be4380e940d7 [2024-06-28 15:50:41] ---> 3a41293b7d08 [2024-06-28 15:50:41] Step 4/11 : WORKDIR /app [2024-06-28 15:50:41] ---> Running in 72ccb80052b0 [2024-06-28 15:50:41] Removing intermediate container 72ccb80052b0 [2024-06-28 15:50:41] ---> 0a3b48ca98a4 [2024-06-28 15:50:41] Step 5/11 : COPY . /app [2024-06-28 15:50:41] ---> c65a7a2ec8a7 [2024-06-28 15:50:41] Step 6/11 : RUN pip install --no-cache-dir -r requirements.txt [2024-06-28 15:50:41] ---> Running in 80ce5ba93784 [2024-06-28 15:50:41] Collecting Flask==2.2.2 [2024-06-28 15:50:41] Downloading Flask-2.2.2-py3-none-any.whl (101 kB) [2024-06-28 15:50:41] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 101.5/101.5 kB 1.9 MB/s eta 0:00:00 [2024-06-28 15:50:41] Collecting suds [2024-06-28 15:50:41] Downloading suds-1.1.2-py3-none-any.whl (144 kB) [2024-06-28 15:50:41] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 144.8/144.8 kB 4.7 MB/s eta 0:00:00 [2024-06-28 15:50:41] Collecting pymysql==1.0.2 [2024-06-28 15:50:41] Downloading PyMySQL-1.0.2-py3-none-any.whl (43 kB) [2024-06-28 15:50:41] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 43.8/43.8 kB 164.2 MB/s eta 0:00:00 [2024-06-28 15:50:41] Collecting requests==2.28.1 [2024-06-28 15:50:41] Downloading requests-2.28.1-py3-none-any.whl (62 kB) [2024-06-28 15:50:41] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.8/62.8 kB 157.9 MB/s eta 0:00:00 [2024-06-28 15:50:41] Collecting xmltodict==0.12.0 [2024-06-28 15:50:41] Downloading xmltodict-0.12.0-py2.py3-none-any.whl (9.2 kB) [2024-06-28 15:50:41] Collecting click>=8.0 [2024-06-28 15:50:42] Downloading click-8.1.7-py3-none-any.whl (97 kB) [2024-06-28 15:50:42] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 97.9/97.9 kB 23.7 MB/s eta 0:00:00 [2024-06-28 15:50:42] Collecting Jinja2>=3.0 [2024-06-28 15:50:42] Downloading jinja2-3.1.4-py3-none-any.whl (133 kB) [2024-06-28 15:50:42] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 133.3/133.3 kB 27.1 MB/s eta 0:00:00 [2024-06-28 15:50:42] Collecting itsdangerous>=2.0 [2024-06-28 15:50:42] Downloading itsdangerous-2.2.0-py3-none-any.whl (16 kB) [2024-06-28 15:50:42] Collecting importlib-metadata>=3.6.0 [2024-06-28 15:50:42] Downloading importlib_metadata-8.0.0-py3-none-any.whl (24 kB) [2024-06-28 15:50:42] Collecting Werkzeug>=2.2.2 [2024-06-28 15:50:42] Downloading werkzeug-3.0.3-py3-none-any.whl (227 kB) [2024-06-28 15:50:42] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 227.3/227.3 kB 22.8 MB/s eta 0:00:00 [2024-06-28 15:50:42] Collecting charset-normalizer<3,>=2 [2024-06-28 15:50:42] Downloading charset_normalizer-2.1.1-py3-none-any.whl (39 kB) [2024-06-28 15:50:42] Collecting certifi>=2017.4.17 [2024-06-28 15:50:42] Downloading certifi-2024.6.2-py3-none-any.whl (164 kB) [2024-06-28 15:50:42] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 164.4/164.4 kB 102.8 MB/s eta 0:00:00 [2024-06-28 15:50:42] Collecting idna<4,>=2.5 [2024-06-28 15:50:43] Downloading idna-3.7-py3-none-any.whl (66 kB) [2024-06-28 15:50:43] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 66.8/66.8 kB 185.5 MB/s eta 0:00:00 [2024-06-28 15:50:43] Collecting urllib3<1.27,>=1.21.1 [2024-06-28 15:50:43] Downloading urllib3-1.26.19-py2.py3-none-any.whl (143 kB) [2024-06-28 15:50:43] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 143.9/143.9 kB 76.7 MB/s eta 0:00:00 [2024-06-28 15:50:43] Collecting zipp>=0.5 [2024-06-28 15:50:43] Downloading zipp-3.19.2-py3-none-any.whl (9.0 kB) [2024-06-28 15:50:43] Collecting MarkupSafe>=2.0 [2024-06-28 15:50:43] Downloading MarkupSafe-2.1.5-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (25 kB) [2024-06-28 15:50:43] Installing collected packages: zipp, xmltodict, urllib3, suds, pymysql, MarkupSafe, itsdangerous, idna, click, charset-normalizer, certifi, Werkzeug, requests, Jinja2, importlib-metadata, Flask [2024-06-28 15:50:44] Successfully installed Flask-2.2.2 Jinja2-3.1.4 MarkupSafe-2.1.5 Werkzeug-3.0.3 certifi-2024.6.2 charset-normalizer-2.1.1 click-8.1.7 idna-3.7 importlib-metadata-8.0.0 itsdangerous-2.2.0 pymysql-1.0.2 requests-2.28.1 suds-1.1.2 urllib3-1.26.19 xmltodict-0.12.0 zipp-3.19.2 [2024-06-28 15:50:44] [2024-06-28 15:50:44] [notice] A new release of pip is available: 23.0.1 -> 24.1.1 [2024-06-28 15:50:44] [notice] To update, run: pip install --upgrade pip [2024-06-28 15:50:45] Removing intermediate container 80ce5ba93784 [2024-06-28 15:50:45] ---> 059a1bddf3fe [2024-06-28 15:50:45] Step 7/11 : RUN pip install --upgrade pip [2024-06-28 15:50:45] ---> Running in a7b634af2659 [2024-06-28 15:50:46] Requirement already satisfied: pip in /env/lib/python3.9/site-packages (23.0.1) [2024-06-28 15:50:46] Collecting pip [2024-06-28 15:50:46] Downloading pip-24.1.1-py3-none-any.whl (1.8 MB) [2024-06-28 15:50:46] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.8/1.8 MB 9.9 MB/s eta 0:00:00 [2024-06-28 15:50:46] Installing collected packages: pip [2024-06-28 15:50:46] Attempting uninstall: pip [2024-06-28 15:50:46] Found existing installation: pip 23.0.1 [2024-06-28 15:50:47] Uninstalling pip-23.0.1: [2024-06-28 15:50:47] Successfully uninstalled pip-23.0.1 [2024-06-28 15:50:48] Successfully installed pip-24.1.1 [2024-06-28 15:50:49] Removing intermediate container a7b634af2659 [2024-06-28 15:50:49] ---> fa78718e674f [2024-06-28 15:50:49] Step 8/11 : EXPOSE 4600 [2024-06-28 15:50:49] ---> Running in 40cff12d7622 [2024-06-28 15:50:49] Removing intermediate container 40cff12d7622 [2024-06-28 15:50:49] ---> 929306d6b6b4 [2024-06-28 15:50:49] Step 9/11 : ENV FLASK_APP=fpxz.py [2024-06-28 15:50:49] ---> Running in 4f7a66882cba [2024-06-28 15:50:49] Removing intermediate container 4f7a66882cba [2024-06-28 15:50:49] ---> f0b2431a2099 [2024-06-28 15:50:49] Step 10/11 : ENV FLASK_RUN_HOST=0.0.0.0 [2024-06-28 15:50:49] ---> Running in 98635fec459b [2024-06-28 15:50:49] Removing intermediate container 98635fec459b [2024-06-28 15:50:49] ---> 8a36b1f2a5c5 [2024-06-28 15:50:49] Step 11/11 : CMD ["flask", "run"] [2024-06-28 15:50:49] ---> Running in 6088d03ced3a [2024-06-28 15:50:49] Removing intermediate container 6088d03ced3a [2024-06-28 15:50:49] ---> e0c6d59b16d0 [2024-06-28 15:50:49] Successfully built e0c6d59b16d0 [2024-06-28 15:50:49] Successfully tagged ccr.ccs.tencentyun.com/tcb-******-hljm/ca-bugxylvt_fpxz:fpxz-006-20240628155022 [2024-06-28 15:50:49] [Pipeline] } [2024-06-28 15:50:49] [Pipeline] // stage [2024-06-28 15:50:49] [Pipeline] stage [2024-06-28 15:50:49] [Pipeline] { (推送 Docker 镜像到 TCR) [2024-06-28 15:50:49] [Pipeline] sh [2024-06-28 15:50:50] + docker push ccr.ccs.tencentyun.com/tcb-******-hljm/ca-bugxylvt_fpxz:fpxz-006-20240628155022 [2024-06-28 15:50:50] The push refers to repository [ccr.ccs.tencentyun.com/tcb-******-hljm/ca-bugxylvt_fpxz] [2024-06-28 15:50:50] fd55c07cd75c: Preparing [2024-06-28 15:50:50] 1cd0a14c8ec9: Preparing [2024-06-28 15:50:50] e797af9b0537: Preparing [2024-06-28 15:50:50] 6c4efffe00c5: Preparing [2024-06-28 15:50:50] 63aa8a2853d0: Preparing [2024-06-28 15:50:50] 96bc6bc13d2f: Preparing [2024-06-28 15:50:50] 8b2d7b261e2c: Preparing [2024-06-28 15:50:50] 7d4e4b165042: Preparing [2024-06-28 15:50:50] 9a9d1a3508f5: Preparing [2024-06-28 15:50:50] 1387079e86ad: Preparing [2024-06-28 15:50:50] 8b2d7b261e2c: Layer already exists [2024-06-28 15:50:50] 1387079e86ad: Layer already exists [2024-06-28 15:50:50] 7d4e4b165042: Layer already exists [2024-06-28 15:50:50] 96bc6bc13d2f: Layer already exists [2024-06-28 15:50:50] 9a9d1a3508f5: Layer already exists [2024-06-28 15:50:51] e797af9b0537: Pushed [2024-06-28 15:50:51] 6c4efffe00c5: Pushed [2024-06-28 15:50:53] 1cd0a14c8ec9: Pushed [2024-06-28 15:50:55] 63aa8a2853d0: Pushed [2024-06-28 15:50:55] fd55c07cd75c: Pushed [2024-06-28 15:50:56] fpxz-006-20240628155022: digest: sha256:2f682e3a780154004c701f7edbf0f4287c016b87b626a8aa2f9df181273f9382 size: 2418 [2024-06-28 15:50:56] [Pipeline] } [2024-06-28 15:50:56] [Pipeline] // stage [2024-06-28 15:50:56] [Pipeline] } [2024-06-28 15:50:56] [Pipeline] // node [2024-06-28 15:50:56] [Pipeline] End of Pipeline [2024-06-28 15:50:56] Finished: SUCCESS *** -----------构建fpxz-006----------- 2024-06-28 15:50:23 create_build_image : succ, 2024-06-28 15:51:01 create_eks_virtual_service : succ, 2024-06-28 15:51:01 check_build_image : succ, , -----------服务fpxz部署fpxz-006----------- 2024-06-28 15:51:02 check_eks_virtual_service : process, DescribeVersion_user_error_Back-off restarting failed container, [service]:[Failed to pull image "ccr.ccs.tencentyun.com/tcb_prd/coredns:amd64-1.10.1-cloudrun": rpc error: code = Unknown desc = failed to pull and unpack image "ccr.ccs.tencentyun.com/tcb_prd/coredns:amd64-1.10.1-cloudrun": failed to copy: httpReaderSeeker: failed open: failed to do request: Get "http://ccr-avatar-sh-1258344699.cos-internal.ap-shanghai.tencentcos.cn/avatar/data/blob/sha256/d7/d78db2b57cc6b7f8c2dadb1b27d712071d02370ec969748d6f03f10b87efe619?q-sign-algorithm=sha1&q-ak=AKIDysfRH0aYzdEs9GF4f6LOI4g6KK8pRAvb&q-sign-time=1719561095%3B1719562295&q-key-time=1719561095%3B1719562295&q-header-list=host&q-url-param-list=&q-signature=f5ec48c6157489dbaf88453adc5a1271d47b2442": dial tcp: lookup ccr-avatar-sh-1258344699.cos-internal.ap-shanghai.tencentcos.cn: no such host,Error: ErrImagePull,Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "fpxz-006" in Pod "fpxz-006-fcff7c6cc-pnv65_rcwhxhhc(f97b335f-f8d7-4309-94aa-6f96b0488816)" failed - error: command '/bin/sh /app/cert/initenv.sh' exited with 137: + certFile=/app/cert/certificate.crt + certLog=/app/cert.log + srcIp=169.254.10.1 + srcHost=api.weixin.qq.com + checkFileCnt=0 + is_user_root + id -u + [ 0 -eq 0 ] + echo User is root, patching env and certs. + [ ! -f /app/cert/certificate.crt ] + [ ! -f /etc/os-release ] + . /etc/os-release + PRETTY_NAME=Debian GNU/Linux 12 (bookworm) + NAME=Debian GNU/Linux + VERSION_ID=12 + VERSION=12 (bookworm) + VERSION_CODENAME=bookworm + ID=debian + HOME_URL=https://www.debian.org/ + SUPPORT_URL=https://www.debian.org/support + BUG_REPORT_URL=https://bugs.debian.org/ + echo [I]: os release is debian + update-ca-certificates -h + cp /app/cert/certificate.crt /usr/local/share/ca-certificates/ + update-ca-certificates , message: "/usr/sbin/update-ca-certificates: [--verbose] [--fresh]\nUpdating certificates in /etc/ssl/certs...\n+ certFile=/app/cert/certificate.crt\n+ certLog=/app/cert.log\n+ srcIp=169.254.10.1\n+ srcHost=api.weixin.qq.com\n+ checkFileCnt=0\n+ is_user_root\n+ id -u\n+ [ 0 -eq 0 ]\n+ echo User is root, patching env and certs.\n+ [ ! -f /app/cert/certificate.crt ]\n+ [ ! -f /etc/os-release ]\n+ . /etc/os-release\n+ PRETTY_NAME=Debian GNU/Linux 12 (bookworm)\n+ NAME=Debian GNU/Linux\n+ VERSION_ID=12\n+ VERSION=12 (bookworm)\n+ VERSION_CODENAME=bookworm\n+ ID=debian\n+ HOME_URL=https://www.debian.org/\n+ SUPPORT_URL=https://www.debian.org/support\n+ BUG_REPORT_URL=https://bugs.debian.org/\n+ echo [I]: os release is debian\n+ update-ca-certificates -h\n+ cp /app/cert/certificate.crt /usr/local/share/ca-certificates/\n+ update-ca-certificates\n",Error: ImagePullBackOff,Back-off restarting failed container,]
06-28置顶一个服务多个端口要怎么实现？
我的主服务是8080，里面还有一个websocket端口8081，但是他只支持暴露 一个端口 我现在是要多部署一个服务吗？
06-28置顶云托管如何使用腾讯云上的对象存储和数据库mysql？
云托管如何使用腾讯云上的对象存储和mysql？需要购买互联资源包吗？
06-28置顶微信小程序(前端)向部署在微信云托管中的springboot服务发送wx.request为什么不通？
背景：目前我的springboot服务部署在微信云托管中，此时我的小程序直接在微信开发者工具中访问springboot服务的公网地址是可以访问的，但是当上传为体验版就请求失败，这是怎么回事？ 问题1、我现在有一个spirngboot程序部署在了微信云托管中，我的微信小程序也要再次部署在微信云托管中，才能使得小程序访问springboot服务的公网/内网地址吗？ 问题2、必须使用[代码]wx.cloud.callContainer来替换wx.request才能通吗。[代码] [代码]求大佬赐教！[代码] [代码]补充：1、[代码]微信云托管中的内网地址输入到小程序网页后台中的requests合法域名中时，提示要我网址备案，这种部署在云托管中的内网网址也要备案吗？还有如果输入公网地址，就提示不能使用公网地址，仅测试可用。怎么办呀，难道真去备案? 补充：2、如果使用[代码]x.cloud.callContainer[代码]，那么我目前开发的微信小程序的前端js代码全部都要有修改，感觉工作量比较大，偏向于不修改代码但使其联通。
06-26
已找到原因：错把云调用的 data 格式请求发到HTTP API. API 有自己的具体参数。