I'm experimenting with this too and it isn't working for me either.

Using Windows, I have my tiddlywiki in a folder called mywiki.
csr.pem, key.pem and server.crt are ALL in the mywiki folder

using this command to start:
tiddlywiki mywiki --listen tlscert=server.crt tlskey=key.pem host=0.0.0.0 
--verbose

I get:
Serving on http://0.0.0.0:8080
(press ctrl-C to exit)
Boot log:
  Startup task: load-modules
  Startup task: info after: load-modules before: startup
  Startup task: startup after: load-modules
  Startup task: story after: startup
  Startup task: commands platforms: node after: story
 syncer-server-filesystem: Dispatching 'save' task: $:/StoryList
 filesystem: Saved file 
C:\Users\skingery\OneDrive\TiddlyWikiNode\mywiki\tiddle
rs\$__StoryList.tid

So it is working on plain ol' http but not on https. Assuming I created the 
certs correctly, what am I missing?

tiddlywiki --version
5.1.19


On Friday, December 28, 2018 at 1:28:36 PM UTC-8, Ron Ropp wrote:
>
> Thought I followed the "using https" guidelines but it appears to be still 
> only listening on 8080 and http. 
>
> Does node version of Tiddlywiki need to be handled differently. I updated 
> to 5.1.19 via npm update and everything else is pretty vanilla. (created 
> the cert and key, etc) all on Linux and node 8.12.0
>
> I also tried to use the port setting to 443 and that threw an error. 
>
> My command matches the tiddlywiki page exactly, and it starts without an 
> error but just http on 8080
>
> Apologies if I am missing something obvious. 
>
> Ron
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/70a3d4d3-66c4-4b20-ac1d-e14c1911659a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to