I started my tiddlywiki nodejs server the normal way with the `tiddlywiki` command. In fact it had been running for a couple weeks.
I did the same as with the standalone - just dragged the downloaded tid onto the nodejs servers page and reloaded. Start there and see if all the other problems are solved. If not let me know but there shouldn't be any need to open additional ports. I think `npm start` is for development purposes - ie if you were going to directly make changes to the code of the plugin itself. For using the plugin just add it to a running wiki like you would any other plugin. > 1. Do you start the media server with '*npm start*' from the ' > *TheDiveO*' directory? Do you get any message like the ones I have in > my print screen above? Is the media server using the same port (8080) > than > your tiddlywiki instance (not me)? > 2. I am using a dedicated linux user (non-sudo) owning the Tiddlywiki > directory, is the same for you? > 3. My tiddlywiki is behind a proxy (nginx), forwarding port 443 to > Tiddlywiki listening on port 8080. I didn't configure any port on the > proxy for the media server (on port 8090). Do you I have to? If so, how > different the server name would be from the Tiddlywiki one > > >>> >>> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/154eeecf-f580-4052-bc6f-d26891471843n%40googlegroups.com.
