-
-
Notifications
You must be signed in to change notification settings - Fork 792
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
Remote Control Plugin doesn't work with proxy #3597
Comments
Thanks for adding your first issue to Stellarium. If you have questions, please do not hesitate to contact us. |
You have someone service on this port already |
I have no service running on this port.I tried other ports. The prompt is the same error. |
I started trying it with root user just now. Can run normally |
My user is in the root group, I don't know what caused it. |
I see no problem in my linux with common user |
I figure out what the reason for this problem is. The reason is that I have opened a global proxy. There is this line in the log. |
If you mean the two
|
I am very curious why after opening a global proxy, opening the remote control plugin will fail. I read a little remote control plugin code and didn't look carefully. Isn't the http service of this remote control plugin run independently? |
You can see the call to But I don't really know this code, so you'll have to study it more thoroughly to understand what's going on. |
When I turned on Remote Control Plugin, the console prompts the binding port to fail when starting.The following is the prompt message:
Loaded plugin "RemoteControl" RemoteControl using QtWebApp version 1.6.4-stellarium StaticFileController: docroot=/usr/share/stellarium/webroot, encoding=UTF-8, maxAge=60 StaticFileController: cache timeout=60000, size=1048576 RemoteControl enabled HttpListener: Cannot bind on port 10109: Operation on socket is not supported Loaded plugin "RemoteSync" stel.plugin.remoteSync: Plugin initialized
System:Arch Linux-6.7.0
StellariumVersion:24.4
Graphics:Nvidia(DriverVersion:545.29.06)
The text was updated successfully, but these errors were encountered: