FpffUVROGDdATCp Posted September 12, 2020 Report Share Posted September 12, 2020 Well listen guys i understand that you try to improve security and now it is not possible to use port 7178 webadminconsole. But under linux port 7179 now dont work also . Server listen this port but browser cannot connect to it at all. tcp 0 0 0.0.0.0:7111 0.0.0.0:* LISTEN 7599/plasticd tcp 0 0 127.0.0.1:7178 0.0.0.0:* LISTEN 7599/plasticd tcp 0 0 0.0.0.0:8087 0.0.0.0:* LISTEN 7599/plasticd tcp 0 0 0.0.0.0:8088 0.0.0.0:* LISTEN 7599/plasticd tcp6 0 0 :::7179 :::* LISTEN 7599/plasticd When you star browser and point to https://serverip:7179 under linux it silently fail to connect. Your let say "security improvements" forcing to create weird constructions like installation nginx proxy on vcs server only to make possible to access 127.0.0.1:7178. I am absolutely not get what point to make such strange decisions like forcing to listen 127.0.0.1. Because quite a normal practice is to have nginx on separate server and redirect to http port on internal server. If before construction looked like: NGINX -> SCM, now it is look like NGINX -> NGINX -> SCM. It is absolutely stupid. Link to comment Share on other sites More sharing options...
calbzam Posted September 14, 2020 Report Share Posted September 14, 2020 Hi, Does the last answer of the following thread could also explain your problem? Regards, Carlos. Link to comment Share on other sites More sharing options...
FpffUVROGDdATCp Posted October 1, 2020 Author Report Share Posted October 1, 2020 Any way to return http management port ? Link to comment Share on other sites More sharing options...
calbzam Posted October 1, 2020 Report Share Posted October 1, 2020 Hi, Aren't you able to access to the webadmin via https (7179 port)? Could you clarify the details of your scenario? Regards, Carlos. Link to comment Share on other sites More sharing options...
DocDyn Posted October 4, 2020 Report Share Posted October 4, 2020 I had similar issue. My error-log showed that the ip wasn't able to bind and with a quick change of the port the error was gone. However now I'm also not able to connect to my admin via https://local-network-ip:xxxx (I changed the port in the address to the newly specified port) I'm not sure if this is the same issue but this started after I updated the plastic server after a while. Link to comment Share on other sites More sharing options...
calbzam Posted October 5, 2020 Report Share Posted October 5, 2020 Hi, Which package did you install exactly? plasticscm-server-core This is based on Mono 4. It is unable to serve the WebUI through SSL because of Mono limitations, and thus, it can't be accessed from outside localhost. We intend to deprecate this package soon. plasticscm-server-netcore This is based on .NET Core 3. It is able to server the WebAdmin through SSL, and thus, it can be accessed from outside localhost. Regards, Carlos. Link to comment Share on other sites More sharing options...
mjensen Posted October 12, 2020 Report Share Posted October 12, 2020 Hi calbzam, thanks for the reply. I think I installed plasticscm-server-core so that might very well be why I can't get it to work. I will try with plasticscm-server-netcore instead. Link to comment Share on other sites More sharing options...
calbzam Posted October 13, 2020 Report Share Posted October 13, 2020 Ok, thanks for the update. Regards, Carlos. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now