My barely educated guess: tiddlywiki still relies on nginx to connect to the video. The src has to be in a place that is accessible to nginx. Therefore you should be able to add that directory location onto a web address and have nginx serve it directly, like an external image.
One way to troubleshoot would be to bring up your Web Developer network tools (method depends on browser) and see what address your browser is trying to connect to in order to see the video. My guess is the src you have in your code is not accessible to nginx in that format. Think of the video as an external image that tiddlywiki is linking to. One thing you could do is make sure the video plays with a direct link and then put that link as the src. So make sure you can play the video at "https://mysite.com/dir/to/video.mp4 and then put that direct link as your src. Once you know it works you can play with relative links but those are generally a whole different beast to contend with. On Tuesday, December 8, 2020 at 3:52:24 PM UTC-5 [email protected] wrote: > Ok, so I Removed the TwTube plugin from control panel, uninstalled the > media server (npm uninstall) and even removed the 'TheDiveO' directory from > 'plugins' to start fresh. > Restarted my tiddlywiki server. > > Everything seems to be clean at this stage. > > I dragged the plugin from 'Download' of this source > <https://thediveo.github.io/TwTube/> to my tiddlywiki. Success, I see > the plugin installed in my control panel. > > My test tiddler however still shows an error message (see below). I tried > moving the .mp4 file to different locations: within mywiki root; within a > 'media' directory under mywiki root; within the 'tiddlers' folder; within a > 'media' directory within the 'tiddlers' folder. > > My video files has permissions 644 and is owned by the tiddlywiki's user, > like all others tiddlers. > > All unsuccessful... :( > > [image: twtube tiddler.png] > Thanks again. > Le mardi 8 décembre 2020 à 09:33:43 UTC-5, [email protected] a écrit : > >> 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/b89d2377-64b2-4d78-b7ba-2ced02e7320en%40googlegroups.com.
