-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pain with setting base url when needed access from outside by public ip and inside network by internal ip #21007
Comments
set |
then it does not work from inside. And I cannot set that url from outside via web console because I cannot access to console from remote. | can see that server works via wget localhost:3000 but not from 192.168.2.12:3000 |
That's another issue which has been reported in #19345 |
please help: what should i do when internal access URL is http://192.168.2.12:3000/ |
I will try to answer some questions, and at the same time, you could understand more about your system and environment.
Since Gitea shows AppURL is just for UI display and URL construction, it does nothing to the Listen address. If user can not access it, please check your firewall (nat, etc) or other rules.
Which address?
If Gitea is listening on "0.0.0.0:3000", it should work. Check your firewall and environment. Plenty of users use the same setting and do not have such problem, and there doesn't seem to be a problem indeed. |
Yep, you was rigth about firewall, despite iptables-save was empty, some rules still persisted. |
Description
when starting configuration server listens localhost and not 0.0.0.0 as stating in its log, so
2022/08/31 10:29:54 cmd/web.go:217:listen() [I] [630f0df2] Listen: http://0.0.0.0:3000
2022/08/31 10:29:54 cmd/web.go:221:listen() [I] [630f0df2] AppURL(ROOT_URL): http://localhost:3000/
is just confusing. User cannot connect to server from outside to initial configuration
when setting addres from local net as AppURL e.g. 192.168.2.12:3000 server actually does not listen to that address, but continues response on localhost:3000.
user cannot connect to both external and internal addresses of a server
Gitea Version
1.17.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
initial run via command line, next was planned to run via systemd
Database
No response
The text was updated successfully, but these errors were encountered: