[Bug] 搭建好了需要开启HTTPS才能正常用
Describe the bug
A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Deployment
- [ ] Docker
- [ ] Vercel
- [ ] Server
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
Smartphone (please complete the following information):
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
Additional Logs Add any logs about the problem here.
Bot detected the issue body's language is not English, translate it automatically.
Title: [Bug] After setting up, you need to enable HTTPS to use it normally.
@bigmn666 Hi, could you please tell me when did you deploy the service first time? you can follow this instructions to resolve this issue https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web/issues/3573#issuecomment-1867126500
我昨天下午16点(东八区)部署, 修改域名为nicochat避免和chatgpt过度类似, 绑定自己的域名后也被标记了.
Bot detected the issue body's language is not English, translate it automatically.
I deployed at 16:00 yesterday afternoon (East 8th District) and changed the domain name to nicochat to avoid being too similar to chatgpt. After binding my own domain name, it was also marked.
我昨天下午16点(东八区)部署, 修改域名为nicochat避免和chatgpt过度类似, 绑定自己的域名后也被标记了.
Let me double confirm is this your first time deploying on a completely new domain?
我昨天下午16点(东八区)部署, 修改域名为nicochat避免和chatgpt过度类似, 绑定自己的域名后也被标记了.
Let me double confirm is this your first time deploying on a completely new domain?
yes, forked it to my github, changed some chatgpt stuff, then bind to chat.mydomain.com after about 3 hour is makrd unsafe by both microsoft smart screen and firefox.
btw, i have changed the chatgpt logo after i reported to microsoft and google.
btw, i have changed the chatgpt logo after i reported to microsoft and google.
Bro, I think your domain was previously flagged by Google before you bought it, and I would suggest the site not to use chat,gpt similar names
Please feel free to comment if you still encounter similar issue. Close for not active reporting same issue