Brettv

Hi All So i am finally back up and running. A trap that i also found myself in was my ISP also changing me to a new static IP address. (i suspect maybe due to all the port 80 hits?) Not sure, but it took me forever to figure this out, as my IP has not changed in years. I installed the nginx docker. Copied over my config files from the letsencrypt config folder Used - docker exec -it letsencrypt /bin/bash/ to get into the letsencrypt container so i could use certbot I then used a certbot command to manually obtain certificates for my domains (similar to what is posted here https://serverfault.com/questions/750902/how-to-use-lets-encrypt-dns-challenge-validation) Note this method does not use the API, you are required to log into your hosting and manually add in TXT records to your DNS zone editor. Once that was complete, i copied out the 4 files (from the archive folder not the symlinks) and pasted them into my config folder on my cache drive where i could access them. I then created a letsencrypt folder under my nginx/keys folder (so it looks like /nginx/keys/letsencrypt) Then i copied the fullchain.pem and privkey.pem files that were created by certbot there. I then stopped the letsencrypt container, and started the nginx container and it seemed to work / pickup where i had left. This did involve some trial and error, but that is mainly because i am not very familiar with what i am doing. In my case, i will need to manually renew the certs and repeat the same procedure in 3 months, but hopefully by then a solution to TLS is found. Cheers Brett

Hi All, I have been able to bash into the container and manually obtain certs with certbot and adding the DNS entries manually, as my domain provider doesnt have an API. With the certs that are generated, i copied them into the letsencrypt folder, where the config files point. However, that doesnt seem to be enough, and i must still be missing a step. Restarting the container deletes the certs as expected. Can anyone shed any light on what i might be missing?

This might be a dumb question, but if i had a VPN, would that get around my ISP blocking port 80?

Im getting the same, i believe my ISP is blocking port 80, which is causing the timeout.

its working now. Must have taken a bit longer for it to update

hmmm it still seems to only show user and group ID for me. I can see that the XML file has been updated, but for some reason it wont update the screen. i tried rebooting, and reinstalling the plugin and got the same result..

Should this be fixed by now? (or do i need to do something separate to refresh?)

Im having the same issue, would love to get this going, as I have wanted a home email solution for years!

Thanks, works a treat Cheers

Hi Binhex, Would it be possible to include a CONTEXT PATH variable for nginx reverse proxy support? (Similar to the linuxserver libresonic docker) Cheers Brett

Me too!

Yep, that fixed it for me, thanks guys.

Hi Team, It seems as though, after the latest docker update booksonic is now getting 500 internal server errors. I tried deleting my config, container etc and reinstalling, but am still having the same problem. Here is an excerpt from my log with the error at org.eclipse.jetty.server.Dispatcher.error(Dispatcher.java:81)at org.eclipse.jetty.server.handler.ErrorHandler.doError(ErrorHandler.java:119)at org.eclipse.jetty.server.handler.ErrorHandler.handle(ErrorHandler.java:78)at org.eclipse.jetty.server.Response.sendError(Response.java:655)at org.eclipse.jetty.server.handler.AbstractHandler.doError(AbstractHandler.java:100)at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1247)at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:168)at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:166)at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1155)at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:219)at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)at org.eclipse.jetty.server.Server.handle(Server.java:564)at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:358)at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:279)at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:110)at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124)at org.eclipse.jetty.util.thread.Invocable.invokePreferred(Invocable.java:128)at org.eclipse.jetty.util.thread.Invocable$InvocableExecutor.invoke(Invocable.java:222)at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:294)at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:199)at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:672)at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:590)at java.lang.Thread.run(Thread.java:748)Caused by:java.lang.NullPointerExceptionat org.apache.jasper.compiler.Validator$ValidateVisitor.<init>(Validator.java:515)at org.apache.jasper.compiler.Validator.validateExDirectives(Validator.java:1853)at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:219)at org.apache.jasper.compiler.Compiler.compile(Compiler.java:372)at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349)at org.apache.jasper.compiler.Compiler.compile(Compiler.java:333)at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:600)at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:368)at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:385)at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:329)at org.eclipse.jetty.jsp.JettyJspServlet.service(JettyJspServlet.java:112)at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:833)at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:535)at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:566)at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:190)at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:188)at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1253)at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:168)at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:166)at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1155)at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:203)at org.eclipse.jetty.server.Dispatcher.error(Dispatcher.java:81)

Hi everyone, Would it be possible to have this docker added? It looks pretty good. It is from collabora - and their implementation of libreoffice. It also works / hooks in with nextcloud. https://nextcloud.com/collaboraonline/ It seems as though a docker already exists, and it supports apache and nginx reverse proxy Cheers Brett

Hello, I am interested in getting this working, however when i run pwmconfig i get the following root@SERVO:~# pwmconfig # pwmconfig revision 5770 (2009-09-16) This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed root@SERVO:~# My motherboard is a Gigabyte ep43-ud3L Does this mean that I cannot use this for fan control?