Hi, Do you also see some messages on the Erlang command line?
Did you try to connect with http to :8000 and see if there is a redirect to https :8443? If so then Zotonic is listening and responding. If there are errors on the erlang command line and you are on OTP21, then you might need to get a patched OTP install. I just saw someone referring to TLS handshake errors on OTP 21.3. That problem was fixed in 21.3.8.5 Cheers, Marc > On 26 Nov 2019, at 00:11, Java House <java4...@gmail.com> wrote: > > Thank you Marc, > I found the file and changed the listen_ip and dbhost but I cannot connect > using https > Is there some additional step required? > > $ curl -kIv https://10.2.3.14:8443 > * Rebuilt URL to: https://10.2.3.14:8443/ > * Trying 10.2.3.14... > * TCP_NODELAY set > * Connected to 10.2.3.14 (10.2.3.14) port 8443 (#0) > * ALPN, offering h2 > * ALPN, offering http/1.1 > * successfully set certificate verify locations: > * CAfile: /etc/pki/tls/certs/ca-bundle.crt > CApath: none > * TLSv1.3 (OUT), TLS handshake, Client hello (1): > * TLSv1.3 (IN), TLS alert, handshake failure (552): > * error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure > * Closing connection 0 > curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake > failure > > > > > %%% PostgreSQL database defaults. > %%% These are the defaults for the equally named options in your site's > config file. > {dbdatabase, "zotonic"}, > {dbschema, "public"}, > {dbpassword, []}, > {dbuser, "zotonic"}, > {dbport, 5432}, > {dbhost, {10,2,4,11}}, > > %%% By default, Zotonic will create a postgres database for you if it doesn't > %%% already exist, and install tables in it. Uncomment the options below > %%% to prevent that. > % {dbcreate, false}, > % {dbinstall, false}, > > %%% IP address on which Zotonic will listen for HTTP requests. > %%% Always overridden by the ZOTONIC_IP environment variable. > %%% Use 'any' for all IP addresses. > {listen_ip, {10,2,3,14}}, > > > On Monday, November 25, 2019 at 11:27:27 PM UTC+1, Marc Worrell wrote: > Hi Nikolas, > > Try: > > ~/.zotonic/0/zotonic.config > > It should have been installed there by the bin/zotonic script. > > Cheers, Marc > > >> On 25 Nov 2019, at 20:03, Java House <java...@gmail.com <>> wrote: >> >> Hi Marc >> >> where do I find the zotonic.config file? >> I searched and there is nowhere bellow the zotonic directory. >> I found only one copy under docker/zotonic.config but the file has different >> content and I am not using docker. >> >> Best >> Nikolas >> >> >> On Monday, November 25, 2019 at 10:44:11 AM UTC+1, Marc Worrell wrote: >> Hi, >> >> Looks like the ipv6 listener can’t start. >>> =SUPERVISOR REPORT==== 24-Nov-2019::18:36:42.045104 === >>> supervisor: {local,zotonic_sup} >>> errorContext: start_error >>> reason: eprotonosupport >>> offender: [{pid,undefined}, >>> {id,webmachine_mochiweb_v6}, >>> {mfargs, >>> {webmachine_mochiweb,start, >>> [webmachine_mochiweb_v6, >>> [{port,8000}, >>> {ip,any6}, >>> {dispatcher,z_sites_dispatcher}, >>> {dispatch_list,[]}, >>> {backlog,500}, >>> {acceptor_pool_size,75}]]}}, >>> {restart_type,permanent}, >>> {shutdown,5000}, >>> {child_type,worker}] >> >> We check if ipv6 is available and if it is we start the listener. >> This is in zotonic_sup.erl: >> >>> ipv6_supported() -> >>> case (catch inet:getaddr("localhost", inet6)) of >>> {ok, _Addr} -> true; >>> {error, _} -> false >>> end. >> >> Apparently the system pretend there is ip6 but doesn’t really support it. >> >> You can disable starting the ipv6 listener by providing a specific listener >> port instead of ‘any’ in the zotonic.config >> >> Replace this >> >>> %%% IP address on which Zotonic will listen for HTTP requests. >>> %%% Always overridden by the ZOTONIC_IP environment variable. >>> %%% Use 'any' for all IP addresses. >>> {listen_ip, any}, >> >> With this: >> >>> %%% IP address on which Zotonic will listen for HTTP requests. >>> %%% Always overridden by the ZOTONIC_IP environment variable. >>> %%% Use 'any' for all IP addresses. >>> {listen_ip, {0,0,0,0}}, >> >> If this fixes the problem then we can look into a better ipv6 detection >> method. >> One of the methods I am thinking of is by actually opening the port before >> proceeding. >> >> Cheers, Marc >> >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Zotonic developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to zotonic-developers+unsubscr...@googlegroups.com <>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/zotonic-developers/ca77a00c-03aa-4047-a95c-1252dda57db4%40googlegroups.com >> >> <https://groups.google.com/d/msgid/zotonic-developers/ca77a00c-03aa-4047-a95c-1252dda57db4%40googlegroups.com?utm_medium=email&utm_source=footer>. > > > -- > > --- > You received this message because you are subscribed to the Google Groups > "Zotonic developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to zotonic-developers+unsubscr...@googlegroups.com > <mailto:zotonic-developers+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/zotonic-developers/f80ada51-3b9d-48db-8017-e54f6f9c29a8%40googlegroups.com > > <https://groups.google.com/d/msgid/zotonic-developers/f80ada51-3b9d-48db-8017-e54f6f9c29a8%40googlegroups.com?utm_medium=email&utm_source=footer>. -- --- You received this message because you are subscribed to the Google Groups "Zotonic developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to zotonic-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/zotonic-developers/E35D2DC3-0AFE-4167-B0F9-831DCF6A7F23%40me.com.
