微信云托管官网
云托管页面已经找不到任何环境配置,都已经删除。 但是小程序后台仍然显示已托管,如下: [图片] 其中,环境IDprod-9gmbm2eie8715d4f并未在云托管后台。
用这种webshell 这种是不是不能用了。我要公众号上传素材 挂载路径为:[代码]/.tencentcloudbase/wx/cloudbase_access_token[代码]; 有什么办法
字节小程序中使用云托管的对象存储,得公网访问了,怎么才能防治被人恶意刷了?
看官方提供的demo是Web程序,自己的控制台程序是按照官方目录来的,Dockerfile也是,但是部署失败了,不清楚是不是必须要Web应用啊,通信协议也必须是Http
[图片]
云托管环境,打印的是JSON格式日志,比如: {"@timestamp":"2024-09-27T14:50:57.034+08:00","@version":"1","message":"XNIO version 3.8.16.Final","logger_name":"org.xnio","thread_name":"main","level":"INFO","level_value":20000,"caller_class_name":"org.xnio.Xnio","caller_method_name":"","caller_file_name":"Xnio.java","caller_line_number":95} 比如上面这个,查询95可以,查询“9*”也可以,但是使用“*5”去查询的话,就会报错:日志查询失败: 加载 “clsSearchLog” 失败
public static Date getStartOfTheDay() { LocalDate currentDate = LocalDate.now(); // 将当前日期和零点时间合并 LocalDateTime currentDateTime = LocalDateTime.of(currentDate, LocalTime.MIDNIGHT); // 获取0点的Date对象 return Date.from(currentDateTime.atZone(java.time.ZoneId.of("Asia/Shanghai")).toInstant()); } public static Date getEndOfTheDay() { LocalDate currentDate = LocalDate.now(); // 将当前日期和零点时间合并 LocalDateTime currentDateTime = LocalDateTime.of(currentDate, LocalTime.MAX); // 获取0点的Date对象 return Date.from(currentDateTime.atZone(java.time.ZoneId.of("Asia/Shanghai")).toInstant()); } 上面是我的代码,我在零点多一点的时候,执行了以上的代码,并且写了一段这样的日志: log.info("the start date is: {} and the end date is: {}", TimeUtils.getStartOfTheDay(), TimeUtils.getEndOfTheDay()); 打出来的时间却是两天前的: 09/27 00:41:20 blood-sugar-dev-133 2024-09-26T16:41:19.814Z INFO 1 --- [blood-sugar-monitor] [nio-8080-exec-9] c.p.u.h.B.dao.impl.FoodDao : the start date is: Wed Sep 25 16:00:00 GMT 2024 and the end date is: Thu Sep 26 15:59:59 GMT 2024 如果是因为时区问题也可以理解,当前的GMT时间是26号,但是就算这样出来的时间也应该是26的0点-23:59吧?
我的项目是jdk17 如何才能完成
云托管免鉴权支付接口什么时候支持h5支付的场景
提交托管小程序,报如下错误: {"errcode":9402205,"errmsg":"In async processing, please call the corresponding query API to confirm whether it is successful after 1 minute. rid: 66f4fd3e-1a9dd35c-09d9fab0"} 已经好多天了,重试过n次,每次都报这个错误,求大神帮忙解决下,客户要退款了~
云托管啥时候能够支持自家产品 coding.net. 代码源关联?
由于我的产品在南方地区的用户较多,用户需要上传内容到cos,而云托管的cos固定在上海区域,对我大部分的用户不太友好。所以……云托管的对象存储服务能否增加广州地区?
在使用对象存储发现API支持的很少,浏览文件夹的功能不支持,没有办法按文件夹去获取文件列表,这块真是想不明白。
请问小程序端如何获取自己的openid 或unionid? 针对需对是,每个小程序用户会生成自己的图片,图片会上传到云托管的对象存储,这些图片允许自己访问,需要用一个ID(openid 或 unionid)作为文件夹名, 难道我得服务端写一个接口专门返回这个openid ? (openid是在服务端header 头里才有) 我试了wx.login 它只给我返回一个code, 我都用了云托管了,为什么还返回一个code,不是免鉴权了,不应该直接返回相关信息吗?
https://developers.weixin.qq.com/miniprogram/dev/wxcloudrun/src/quickstart/template/official.html // 小程序调用,获取微信 Open ID app.get("/api/wx_openid", async (req, res) => { if (req.headers["x-wx-source"]) { res.send(req.headers["x-wx-openid"]); } }); express 框架模版中以上代码未对x-wx-source进行未获取时返回值的设定,而在本地调试中headers并不包含x-wx-source,所以在前端迟迟得不到返回结果,导致超时连接失败。 而关于官方模板说明、本地调试、开发指引-调用云托管服务-微信小程序关于header的文档说明中,并未提及什么情况下包含x-wx-source,文档搜索后在操作指南中的消息推送模块才提及到“若云托管开启了公网访问,需要验证消息推送的请求头,带 x-wx-source 的请求才是微信侧发起的推送。” 因此是否是本地调试云托管自动生成的wxcloud-localdebug-proxy自动开启的公网访问导致不带x-wx-source,进而导致超时?另外wxcloud-localdebug-proxy自动开启的公网访问的作用是什么?是否有必要?
[InnerError.InternalError]An internal error has occurred. Retry your request, but if the problem persists, contact us.
云托管的收费是不是没有起步价,比如在1天总共只用了1小时cpu就只花1小时的钱,而第二天用了10分钟就花10分钟的钱?又比如运行mysql,每天总共只运行半小时只收半小时的钱? 我只看见有一个要求是低消:低消说明:在按量计费环境内,如果当日有资源使用,且产生的计费金额不足0.01元,将补齐按照0.01元收取。
https://test-120217-6-1329085061.sh.run.tcloudbase.com/ 这是部署好的URL,怎么找到我的部署账户? 除了找不到部署账户外,还有一个问题: 我运托管的服务,有时非常慢,这是为什么?
2024-09-14 18:10:08 check_eks_virtual_service : process, DescribeVersion_user_error_Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "9a1e077e4671441d78ef218b6787c1fcbf611a7bfbf59876b857403ee1f25dc8": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: read init-p: connection reset by peer: unknown, message: "", [service]:[Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "e09f80508bc5abfea2340be1ca3ab9621e9ac7dc39f62b8f036cafd24228a4e2": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: process_linux.go:103: executing setns process caused: exit status 1: unknown, message: "",Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "966cfd74e3aca0a25d9e245226ae5503d0654ea31b18327dca0b0fdf6b7cad24": OCI runtime exec failed: exec failed: cannot exec a container that has stopped: unknown, message: "",Back-off restarting failed container,Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "08d31bba6764e671598d8d90c0d958e8a10d78cd89ceb4590d2b5e6239e0fc1e": OCI runtime exec failed: exec failed: cannot exec a container that has stopped: unknown, message: "",Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "c14845e0fa7a7a9401435c6333093f52fa5e1936fb13cacd8926eef16b4ba968": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: process_linux.go:103: executing setns process caused: exit status 1: unknown, message: "",Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "cc17ee07d384f7c6fcc7b557c96668c7b16f599ed128acaca963aa976e15ffa2": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: process_linux.go:103: executing setns process caused: exit status 1: unknown, message: "",Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "e38654ba14aaeff3c2b12424e848a8678b544df5ca5781de992a4fee9f91399b": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: read init-p: connection reset by peer: unknown, message: "",Exec lifecycle hook ([/bin/sh /app/cert/initenv.sh]) for Container "new2-002" in Pod "new2-002-74c9fcd6bd-5nhln_tiuaxlkk(be6a86f1-8c7f-4460-8f1e-4535a7283bea)" failed - error: rpc error: code = Unknown desc = failed to exec in container: failed to start exec "9a1e077e4671441d78ef218b6787c1fcbf611a7bfbf59876b857403ee1f25dc8": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: read init-p: connection reset by peer: unknown, message: "",]
大佬们可以直接修改云托管服务里的文件吗?每次修改都要重新部署吗?发布成功的容器不支持上传文件吗?怎么停止服务的运行?为什么不支持修改和上传?
都不知道你说啥,是这个路径拿不到?这种webshell是啥啊