Hello, 

Thanks for all your ideas! but nothing worked...

I tried changing the port to 18888 and I got the same error. Also tried 
with sudo just to be sure that's not related with privileges.
Looks like CAS is starting 2 things in the same port, I know it's weird. 
Could anyone share their SSL configuration in order to make gradle-overlay 
works?

FYI:
We are on linux and mac and no other process is in that port.

Regards,
David

On Wednesday, 19 July 2017 21:17:51 UTC+2, Uxío Prego wrote:
>
> You should not be running Java with super user privileges, ever. Specially 
> in 
> production environments. 
>
> When on Linux additional configuration is necessary to allow an operating 
> system level user account access to well known ports in the first 1K 
> range. 
>
> OP likely to have had indeed the port held by a previous instance of CAS. 
>
> > On 19 Jul 2017, at 15:23, Toby Archer <[email protected] <javascript:>> 
> wrote: 
> > 
> > First thing that comes to my mind is checking if there is anything on 
> that port. try running: 
> > 
> > netstat -a | grep "8888" 
> >  That should tell you whether or not there is anything else listening on 
> that port. 
> > 
> > My other thought would be to try and let it be the default 
> configuration, which is 8443 I believe. See if it accepts that. 
> > 
> > Oh, the other thing that occurred to me is try running it as a 
> privileged user, i.e. sudo. Some distros don't let unprivileged users bind 
> to ports below 10000. 
> > 
> > I'm still very much so a rookie at CAS, but hopefully these suggestions 
> will be helpful. Quoth the blind man leading the blind. 
> > 
> > On Wednesday, July 19, 2017 at 2:32:50 AM UTC-5, David Rodriguez 
> Gonzalez wrote: 
> > Good morning everyone, 
> > 
> > I am having problems setting up https in CAS 5.0.x gradle overlay, maybe 
> you could give me a hand. 
> > 
> > I have the following properties in application.yml, keystore properties 
> duplicated to see if it works 
> > 
> > server: 
> >   port: 8888 
> >   ssl: 
> >     enabled: true 
> >     keyStorePassword: changeit 
> >     key-store-password: changeit 
> >     keyPassword: changeit 
> >     key-password: changeit 
> >     keyStore: file:/etc/cas/thekeystore 
> >     key-store: file:/etc/cas/thekeystore 
> > 
> > 
> > But I'm getting this: 
> > 
> > *************************** 
> > APPLICATION FAILED TO START 
> > *************************** 
> > 
> > Description: 
> > 
> > The Tomcat connector configured to listen on port 8888 failed to start. 
> The port may already be in use or the connector may be misconfigured. 
> > 
> > Action: 
> > 
> > Verify the connector's configuration, identify and stop any process 
> that's listening on port 8888, or configure this application to listen on 
> another port. 
> > 
> > 
> > Thanks a lot! 
> > 
> > -- 
> > - CAS gitter chatroom: https://gitter.im/apereo/cas 
> > - CAS mailing list guidelines: 
> https://apereo.github.io/cas/Mailing-Lists.html 
> > - CAS documentation website: https://apereo.github.io/cas 
> > - CAS project website: https://github.com/apereo/cas 
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups "CAS Community" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to [email protected] <javascript:>. 
> > To view this discussion on the web visit 
> https://groups.google.com/a/apereo.org/d/msgid/cas-user/cb1ff7e4-c790-4653-927b-44afcdf14553%40apereo.org.
>  
>
>
>

-- 
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/39424cf9-b5f2-4abf-972b-8417b31b9499%40apereo.org.

Reply via email to