DuanGeGit opened a new issue, #8105:
URL: https://github.com/apache/incubator-seata/issues/8105

   ### Check Ahead
   
   - [x] I have searched the [issues](https://github.com/seata/seata/issues) of 
this repository and believe that this is not a duplicate.
   
   - [ ] I am willing to try to fix this bug myself.
   
   
   ### Ⅰ. Issue Description
   
   1. 官网下载的二进制文件apache-seata-2.5.0-incubating-bin.tar.gz
   2. 
运行apache-seata-2.5.0-incubating-bin\seata-namingserver\bin\seata-namingserver.bat
   3. 运行apache-seata-2.5.0-incubating-bin\seata-server\bin\seata-server.bat
   4. 访问http://localhost:8081报404,如下图所示
   未修改任何配置文件!未修改任何配置文件!未修改任何配置文件!
   
   <img width="1262" height="527" alt="Image" 
src="https://github.com/user-attachments/assets/725f575f-6abb-4fc3-ae09-147efbdddf32";
 />
   
   ### Ⅱ. Describe what happened
   
   1. 官网下载的二进制文件apache-seata-2.5.0-incubating-bin.tar.gz
   2. 
运行apache-seata-2.5.0-incubating-bin\seata-namingserver\bin\seata-namingserver.bat
   3. 运行apache-seata-2.5.0-incubating-bin\seata-server\bin\seata-server.bat
   4. 访问http://localhost:8081报404,如下图所示
   未修改任何配置文件!未修改任何配置文件!未修改任何配置文件!
   
   ### Ⅲ. Describe what you expected to happen
   
   可以正常访问控制台登录页面
   
   ### Ⅳ. How to reproduce it (as minimally and precisely as possible)
   
   1. 官网下载的二进制文件apache-seata-2.5.0-incubating-bin.tar.gz
   2. 
运行apache-seata-2.5.0-incubating-bin\seata-namingserver\bin\seata-namingserver.bat
   3. 运行apache-seata-2.5.0-incubating-bin\seata-server\bin\seata-server.bat
   4. 访问http://localhost:8081报404
   
   ### Ⅴ. Anything else we need to know?
   
   _No response_
   
   ### Ⅵ. Environment
   
   JDK17


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to