本地调试方式运行的?本地调试也是在容器里运行的,但是容器内网络和主机网络是区分开的。可以把mysql address 改为本地的实际 ip,不要使用 127.0.0.1
VSCode本地调试例子程序(Django模版),为什么无法连接本地MariaDB数据库?报错信息如下:(我用本地UI工具HeidiSQL连接没有问题): 连接参数: "envParams": { "MYSQL_USERNAME": "root", "MYSQL_PASSWORD": "kkkkkkkk", "MYSQL_ADDRESS": "127.0.0.1:3306" }, * Executing task: docker run --rm -t --network wxcb0 --name wxcloud_wxcloudrun-django-main -l role=container -l wxcloud=wxcloudrun-django-main -l hostPort=27081 -l wxPort=27082 -p 127.0.0.1:27081:80/tcp -e 'MYSQL_USERNAME=root' -e 'MYSQL_PASSWORD=abc123__' -e 'MYSQL_ADDRESS=127.0.0.1:3306' --cpus 1 -m 2GB --mount type=bind,source="C:\Users\brian\.wxcloudbase\.tencentcloudbase",target=/.tencentcloudbase,readonly wxcloud_wxcloudrun-django-main:latest [2025-04-22 01:42:26,204] [autoreload.py:637] [autoreload:run_with_reloader] [INFO]- Watching for file changes with StatReloader Performing system checks... System check identified some issues: WARNINGS: wxcloudrun.Counters.count: (fields.W122) 'max_length' is ignored when used with IntegerField. HINT: Remove 'max_length' from field wxcloudrun.Counters.createdAt: (fields.W161) Fixed default value provided. HINT: It seems you set a fixed date / time / datetime value as default for this field. This may not be what you want. If you want to have the current date as default, use `django.utils.timezone.now` wxcloudrun.Counters.updatedAt: (fields.W161) Fixed default value provided. HINT: It seems you set a fixed date / time / datetime value as default for this field. This may not be what you want. If you want to have the current date as default, use `django.utils.timezone.now` System check identified 3 issues (0 silenced). Exception in thread django-main-thread: Traceback (most recent call last): File "/root/.local/lib/python3.8/site-packages/pymysql/connections.py", line 613, in connect sock = socket.create_connection( File "/usr/lib/python3.8/socket.py", line 808, in create_connection raise err File "/usr/lib/python3.8/socket.py", line 796, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/root/.local/lib/python3.8/site-packages/django/db/backends/base/base.py", line 219, in ensure_connection self.connect() File "/root/.local/lib/python3.8/site-packages/django/utils/asyncio.py", line 26, in inner return func(*args, **kwargs) File "/root/.local/lib/python3.8/site-packages/django/db/backends/base/base.py", line 200, in connect self.connection = self.get_new_connection(conn_params) File "/root/.local/lib/python3.8/site-packages/django/utils/asyncio.py", line 26, in inner return func(*args, **kwargs) File "/root/.local/lib/python3.8/site-packages/django/db/backends/mysql/base.py", line 234, in get_new_connection connection = Database.connect(**conn_params) File "/root/.local/lib/python3.8/site-packages/pymysql/connections.py", line 353, in __init__ self.connect() File "/root/.local/lib/python3.8/site-packages/pymysql/connections.py", line 664, in connect raise exc pymysql.err.OperationalError: (2003, "Can't connect to MySQL server on '127.0.0.1' ([Errno 111] Connection refused)") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner self.run() File "/usr/lib/python3.8/threading.py", line 870, in run self._target(*self._args, **self._kwargs) File "/root/.local/lib/python3.8/site-packages/django/utils/autoreload.py", line 64, in wrapper fn(*args, **kwargs) File "/root/.local/lib/python3.8/site-packages/django/core/management/commands/runserver.py", line 121, in inner_run self.check_migrations() File "/root/.local/lib/python3.8/site-packages/django/core/management/base.py", line 486, in check_migrations executor = MigrationExecutor(connections[DEFAULT_DB_ALIAS]) File "/root/.local/lib/python3.8/site-packages/django/db/migrations/executor.py", line 18, in __init__ self.loader = MigrationLoader(self.connection) File "/root/.local/lib/python3.8/site-packages/django/db/migrations/loader.py", line 53, in __init__ self.build_graph() File "/root/.local/lib/python3.8/site-packages/django/db/migrations/loader.py", line 220, in build_graph self.applied_migrations = recorder.applied_migrations() File "/root/.local/lib/python3.8/site-packages/django/db/migrations/recorder.py", line 77, in applied_migrations if self.has_table(): File "/root/.local/lib/python3.8/site-packages/django/db/migrations/recorder.py", line 55, in has_table with self.connection.cursor() as cursor: File "/root/.local/lib/python3.8/site-packages/django/utils/asyncio.py", line 26, in inner return func(*args, **kwargs) File "/root/.local/lib/python3.8/site-packages/django/db/backends/base/base.py", line 259, in cursor return self._cursor() File "/root/.local/lib/python3.8/site-packages/django/db/backends/base/base.py", line 235, in _cursor self.ensure_connection() File "/root/.local/lib/python3.8/site-packages/django/utils/asyncio.py", line 26, in inner return func(*args, **kwargs) File "/root/.local/lib/python3.8/site-packages/django/db/backends/base/base.py", line 219, in ensure_connection self.connect() File "/root/.local/lib/python3.8/site-packages/django/db/utils.py", line 90, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/root/.local/lib/python3.8/site-packages/django/db/backends/base/base.py", line 219, in ensure_connection self.connect() File "/root/.local/lib/python3.8/site-packages/django/utils/asyncio.py", line 26, in inner return func(*args, **kwargs) File "/root/.local/lib/python3.8/site-packages/django/db/backends/base/base.py", line 200, in connect self.connection = self.get_new_connection(conn_params) File "/root/.local/lib/python3.8/site-packages/django/utils/asyncio.py", line 26, in inner return func(*args, **kwargs) File "/root/.local/lib/python3.8/site-packages/django/db/backends/mysql/base.py", line 234, in get_new_connection connection = Database.connect(**conn_params) File "/root/.local/lib/python3.8/site-packages/pymysql/connections.py", line 353, in __init__ self.connect() File "/root/.local/lib/python3.8/site-packages/pymysql/connections.py", line 664, in connect raise exc django.db.utils.OperationalError: (2003, "Can't connect to MySQL server on '127.0.0.1' ([Errno 111] Connection refused)")
04-23删除服务、删除环境即可
怎么取消微信云托管?小程序已注销,免费配额已到期,怎么取消微信云托管
04-15如果需要,跳转对应的腾讯云账号后,在腾讯云侧创建secret_id和secret_key,并加入 cos 权限,也是可以用的
如何查询云托管中对象存储的secret_id和secret_key?在哪里能查询我的微信云托管环境中,对象存储服务的 secret_id和secret_key? 在云托管中,可以看到对象存储的桶和地域信息,没有密钥信息。 登录云平台,也没找到对应云托管环境ID
04-14检测 mysql 的内网 ip、端口、登录的用户名和密码
Ping 请求找不到主机 10.24.108.xxx?注册django云托管后不能连接mysql数据库,ping服务器显示找不到主机?
04-11是删除报错还是有什么现象。有报错的话是什么报错信息。
微信云托管的服务列表为什么不能删掉?微信云托管为什么不能删除不需要的服务列表????????
04-10这里没太明白问题。 如果是从小程序中调用云托管服务,直接使用wx.cloud.callContainer 方法即可。使用这个方法的话无需配置域名,在sdk中初始化环境及指明服务即可调用。
微信小游戏助手的网络请求,如何调用云托管服务的接口微信小游戏助手的网络请求,如何调用云托管服务的接口,是不是只能调用公网域名的服务,不能直接配置云托管的环境ID
03-26云开发套餐内的资源未包含云托管的计费项,由于不同资源有不同的计费项,云托管目前是计量了容器实例启动后占用的CPU和MEM资源。 如果不能接受冷启动,除常开外,容器这边还可以通过设置定时触发,让实例在有业务阶段启动,夜间可以允许缩容,这样来调控以降低费用
云托管付费方案有哪些?云托管中的订单详情为云开发资源,那么购买云开发 19.9 字源是否可以提供给云托管使用? 若不能共用,那么云托管是否仅能 使用按量付费? 若按量付费,云托管无法做到 15s 内启动服务器和数据库,导致云托管数据库和服务必须保持常开,无端耗费大量资源。 目前查看,云托管常开24小时费用不低,是否有其他方案进行代替?
03-26还需要你启动进程并在80端口监听,确保http请求能连接到你提供的80端口。
微信云托管应用端口报错,难道不是DockerFile写EXPOSE 80就可以了嘛?发布端口配置80,Dockerfile配置80,但就是报错 2025-03-21 12:51:24 check_eks_virtual_service : process, DescribeVersion_not_ready, [service]:[Readiness probe failed: dial tcp 10.7.0.175:80: connect: connection refused,Liveness probe failed: dial tcp 10.7.0.175:80: connect: connection refused,]
03-21请求的路径有问题,后端是否实现了对请求路径的处理
微信云托管服务,微信小程序访问后端服务报错,cannot find path,什么问题?登录请求失败 Error: cloud.callContainer:fail Error: errCode: -606004errMsg: Cannot find path. For more information, pleaserefer to https://docs.cloudbase.net/error-code/service(callld:1742376576577-0.06067664686734098)(trace17:29:36 start->17:29:36 system error (Error: errCode:-606004errMsg: Cannot find path. For more informationplease refer to https://docs.cloudbase.net/error-code/service), abort)
03-20你用来扫码登录的微信账号,是小程序本身的管理员或者开发者么?
删除了云托管的环境之后,发现不能再以小程序的身份登录了?正常来说,扫码云托管之后,是需要选择用什么账号登录的。但是当我删除了对应小程序的环境之后,发现再次扫码就不能以小程序的身份登录了。 然后从登录了小程序的微信公众号跳转到云托管的时候,又说我名下没有对应的开发者账号。 [图片] [图片]
03-19