Hi guys,

I just installed Ubooquity on my NAS and got it worked with a little help. :)

Now, when I surf into the server and I choose the Comics button

I got to press another button to actually get to the Comics.

Why is that?

Here is also the path in my webbrowser when I see the Comics folders after I press the second button. (The second button appears without the 1):

connect /tmp/.X11-unix/X0: No such file or directory

20150324 09:26:31 [Scanner thread] INFO  com.ubooquity.data.feeder.a - Scanning comics directories
20150324 09:26:31 [Scanner thread] INFO  com.ubooquity.data.database.b - Inserting/updating comic entry in database : /xxxxx
20150324 09:26:31 [Scanner thread] INFO  com.ubooquity.b.c - Reading metadata of comic file: /xxxxx/xxxxx.cbr
20150324 09:26:31 [Scanner thread] INFO  com.ubooquity.data.database.b - Inserting/updating comic entry in database : /xxxxx/xxxxx.cbr
20150324 09:26:33 [Scanner thread] ERROR com.ubooquity.Ubooquity - Uncaught exception on thread: Scanner thread
java.lang.NoClassDefFoundError: Could not initialize class sun.awt.X11GraphicsEnvironment
	at java.lang.Class.forName0(Native Method) ~[na:1.7.0_75]
	at java.lang.Class.forName(Class.java:191) ~[na:1.7.0_75]
	at java.awt.GraphicsEnvironment.createGE(GraphicsEnvironment.java:102) ~[na:1.7.0_75]
	at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:81) ~[na:1.7.0_75]
	at java.awt.image.BufferedImage.createGraphics(BufferedImage.java:1182) ~[na:1.7.0_75]
	at com.ubooquity.f.d.a(SourceFile:124) ~[Ubooquity.jar:1.7.5]
	at com.ubooquity.f.d.a(SourceFile:34) ~[Ubooquity.jar:1.7.5]
	at com.ubooquity.data.feeder.b.a(SourceFile:72) ~[Ubooquity.jar:1.7.5]
	at com.ubooquity.data.feeder.a.b(SourceFile:518) ~[Ubooquity.jar:1.7.5]
	at com.ubooquity.data.feeder.a.c(SourceFile:458) ~[Ubooquity.jar:1.7.5]
	at com.ubooquity.data.feeder.a.b(SourceFile:39) ~[Ubooquity.jar:1.7.5]
	at com.ubooquity.data.feeder.a$1.run(SourceFile:127) ~[Ubooquity.jar:1.7.5]
	at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0_75]

I ran into a strange problem today. I converted a large number of my comic files from CBR to CBZ using 7-zip. I un-rar-ed the files to folders, then zipped them back up using these settings:

7z a -mx0 -mmt4 my_new_comic_file.cbz *.*

a = archive

mx0 = no compression

mmt4 = use all 4 CPU cores

After I zipped up all my files and deleted the old CBRs, I rescanned the folder tree with Ubooquity. It processed the files but many of my newly zipped CBZs were not recognized. When I checked the Ubooquity log, I found errors like this one:

20160125 11:02:15 [Scanner thread] WARN com.ubooquity.f.a - Failed to read file, will try to guess format: M:\eBooks\Comics\Azrael\Azrael v2\Azrael v2 #003.cbz
20160125 11:02:15 [Scanner thread] WARN com.ubooquity.f.a - Failed to guess file format

This happened to a couple hundred files. I went to the specific file and opened it and read it in another reader/viewer (Honeyview), and I couldn't see anything wrong with it. I opened ComicRack and rescanned my folders and the comics showed up fine in ComicRack. Just because I couldn't think of anything else to try I had ComicRack convert the files to CBZ (even though they were already CBZ files). It took a while, but when it was finished, I rescanned with Ubooquity and all bad files comics were fixed.

That leads me to assume that whatever settings that I'm using when I manually zip the files aren't good for Ubooquity. So my question is, what settings should I use? I have a mess more CBRs to convert.

Thanks,
Tom

Hi,

For a week I try to run ubooquity on my surface pro 3. My version of JAVA is the latest.

When I launch the .jar file with Java Web Start Launcher I've this message of error :

Unable to launch Application ( en Francais : Impossible de Lancer l'application )

I've tested it on my macbook and it work fine.

Thanks for your help

best regards

This is details :

org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Contenu non autorisé dans le prologue.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(Unknown Source)
at com.sun.deploy.xml.XMLParser.parse(Unknown Source)
at com.sun.javaws.jnl.XMLFormat.parse(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main.access$000(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

I got tired of the errors from a self-signed certificate and started a project to try and get an HTTPS certificate from Letsencrypt (its free!) working for Ubooquity. Thought I'd share my results and method if anyone else wants to give it a shot. I started with this post here and modified his script to suit my needs. http://blog.ivantichy.cz/blogpost/view/74

A few caveats...

• If your domain is a sub domain on a popular domain, there is a good chance you won't be able to get a certificate, as they are distributed in limited quantities per domain.
• You can't have a service running on port 9999
• If you are running the server at home, your ISP can't be blocking port 443 (used to verify ownership of the domain)

I'm running Ubooquity on Ubuntu Server 14.04.3 LTS, Your mileage may vary with other distros. You'll need some basic terminal skills and sudo.

First, you'll need to install Letsencrypt

#Install Git if needed
apt-get install git
#Create a directory for Letsencrypt
mkdir /opt/letsencrypt
cd /opt
git clone https://github.com/letsencrypt/letsencrypt
cd letsencrypt

You'll may need to edit a file (I did) in /letsencrypt to account for Ubuntu having an older version of Python in the repository. See this post for more info...

https://community.letsencrypt.org/t/insecureplatformwarning-on-ubuntu-14-04-w-python-2-7-6/2871/3

Once this prereqs are done, here is the script you'll need to run. It won't work out of the box so make sure you read the comments and update the info as needed.

Create a script, set it to executable, and paste this in with your preferred editor.

#!/bin/bash
#Original author Ivan Tichy - Original http://blog.ivantichy.cz/blogpost/view/74 -- Updated for Ubooquity by Salty
#Please modify these values according to your environment
certdir=/etc/letsencrypt/live/yourdomain.com/ #just replace the domain name after /live/
keytooldir=/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/ #java keytool located in jre/bin (see this post if you need help finding this dir http://ubuntuforums.org/showthread.php?t=1054731&p=6643281#post6643281 )
letsencryptdir=/opt/letsencrypt/ #letsencrypt directory here
mydomain=yourdomain.com #put your domain name here
myemail=your@email.com #your email
networkdevice=eth0 #your network device  (run ifconfig to get the name)
keystoredir=/home/salty/.keystore #located in home dir of user running Ubooquity
keystorepass=yoursuperstrongpassword #the password for your keystore


#the script itself:
cd /opt/letsencrypt #the location of your letsencrypt install
git pull origin master #update letsencrypt with the latest files


#this temporarily reroutes your traffic to port 443 to port 9999 for the domain ownership test letsencrypt does.  
#it keeps you from having to shut down Ubooq service
iptables -I INPUT -p tcp -m tcp --dport 9999 -j ACCEPT


iptables -t nat -I PREROUTING -i $networkdevice -p tcp -m tcp --dport 443 -j REDIRECT --to-ports 9999


#Leave the top one uncommented for testing, it creates fake certs and won't count against the certificate limit from letsencrypt.  
#Comment out top one and uncomment second command when ready to generate real cert


$letsencryptdir/letsencrypt-auto certonly --verbose --standalone --test-cert --break-my-certs -d $mydomain --standalone-supported-challenges tls-sni-01 --tls-sni-01-port 9999 --renew-by-default --email $myemail --agree-tos
#$letsencryptdir/letsencrypt-auto certonly --standalone -d $mydomain --standalone-supported-challenges tls-sni-01 --tls-sni-01-port 9999 --renew-by-default --email $myemail --agree-tos


#deletes rerouting rule
iptables -t nat -D PREROUTING -i $networkdevice -p tcp -m tcp --dport 443 -j REDIRECT --to-ports 9999
iptables -D INPUT -p tcp -m tcp --dport 9999 -j ACCEPT


#deletes any previous JKS keys
$keytooldir/keytool -delete -alias root -storepass $keystorepass -keystore $keystoredir/ubooq_key.jks
$keytooldir/keytool -delete -alias ubooq_key -storepass $keystorepass -keystore $keystoredir/ubooq_key.jks


#builds a usable keystore from the CA provided by letsencrypt
openssl pkcs12 -export -in $certdir/fullchain.pem -inkey $certdir/privkey.pem -out $certdir/cert_and_key.p12 -name ubooq_key -CAfile $certdir/chain.pem -caname root -password pass:aaa
$keytooldir/keytool -importkeystore -srcstorepass aaa -deststorepass $keystorepass -destkeypass $keystorepass -srckeystore $certdir/cert_and_key.p12 -srcstoretype PKCS12 -alias ubooq_key -keystore $keystoredir/ubooq_key.jks
$keytooldir/keytool -import -trustcacerts -alias root -deststorepass $keystorepass -file $certdir/chain.pem -noprompt -keystore $keystoredir/ubooq_key.jks

Run the script, do whatever tweaking you need, then when you are generating a good fake cert and keystore, swap the commented out lines in the middle and generate your real certificate and keystore. Add the keystore and password to Ubooquity using the admin web interface and you should be good to go. Afterwards, you can add this to a cron job to re-up your certificate when it expires. GLHF!