Sorry I tried to put it in the code box but it didn't work. I thought it was these 'code'
but got it wrong.
Anyway, sadly still no good
I'm sorry, you've given me far more credit than you should have. I've never used docker before and the extent of my terminal knowledge is mostly copy pasting from instructions on software sites.
I followed you up until point four in your last message.
The red text doesn't seem to correspond with the type of format that I got in my previous terminal response.
Oh, I see. Because there are two methods of installing StirlingPDF described in their website, you probably tried the first one which involved downloading some files and now you have two separate, but similarly named folders: StirlingPDF and Stirling-PDF.
This isn't an issue per-se but is probably causing some mix up here. So, to be safe, delete both of them. Note that the one named Stirling-PDF, with a hyphen, is inside your downloads folder.
Start over by creating the necessary folder structure:
mkdir -p StirlingPDF/{trainingData,extraConfigs,customFiles,logs,pipeline}
Stop any containers named "stirling-pdf" as per the last attempt, which would've created it and thus might cause errors due to name collisions, and clear any non-active containers:
docker container stop stirling-pdf
docker container prune
And run it again:
docker run -d \
--name stirling-pdf \
-p 8080:8080 \
-v "/home/admin/StirlingPDF/trainingData:/usr/share/tessdata" \
-v "/home/admin/StirlingPDF/extraConfigs:/configs" \
-v "/home/admin/StirlingPDF/customFiles:/customFiles/" \
-v "/home/admin/StirlingPDF/logs:/logs/" \
-v "/home/admin/StirlingPDF/pipeline:/pipeline/" \
-e DOCKER_ENABLE_SECURITY=false \
-e LANGS=en_GB \
stirlingtools/stirling-pdf:latest
still no success on localhost:8080 or localhost:8081
Im pretty sure that I deleted all the Stirling PDF folders too.
That screenshot is from your desktop, but the previous post showed that you had this SterlingPDF in your home directory (the first shortcut on the sidebar). Are you sure you deleted that as well?
You can create this folder wherever you want, that's not an issue, but you have to adjust the Docker command accordingly.
sorry, im an idiot. There was still a folder in the home directory. let me try those steps again.
thanks so much for your patience.
Ok I deleted it. followed the steps again and still...nothing when I navigate to localhost:8080 or 8081
The only stirling files that I now see are the ones that we just created.
Mmmm strange that you have that lock icon in those folders, that could indicate a permission issue but I'm not sure why it's even showing up. Can you run:
ls -l StirlingPDF
That should return something like this:
drwxr-xr-x 2 c200 c200 4096 Feb 18 17:52 customFiles
drwxr-xr-x 2 c200 c200 4096 Feb 18 17:52 extraConfigs
drwxr-xr-x 2 c200 c200 4096 Feb 18 17:52 logs
drwxr-xr-x 2 c200 c200 4096 Feb 18 17:52 pipeline
drwxr-xr-x 2 c200 c200 4096 Feb 18 17:52 trainingData
My username in this computer with Mint is "c200", so for you I would expect to show as "admin" (I've been assuming that's your username, right?).
yes my username is admin on here. just to make things more difficult for the fun of it!
ah.....I think I may now be understanding the issue. So. I created the original account on this system as User10, that had administrator permissions. I then, to confuse the hackers, because for some reason I seem to think I'm Julian Assange, created a user account without administrator permissions called "admin".
However, in order to get this Stirling PDF working I changed the "admin" permissions to administrator. However, I don't know how this could have actually worked as I did this from the "admin" account anyway. Nothing I can see had changed.
This is the result from the commands you just gave:
Well, this hacker is indeed very confused 
I have to assume at this point this is a permission issue, otherwise I cannot explain what's going on... I just tried myself on this computer and everything went smoothly (yesterday I tried on a virtual machine with Zorin OS).
Once again, you'll have to stop the container and prune them:
docker container stop stirling-pdf
docker container prune
And this time, let's create a whole new folder elsewhere just to be absolutely sure it's brand new. For example, in your desktop:
mkdir -p /home/admin/Desktop/StirlingPDF/{trainingData,extraConfigs,customFiles,logs,pipeline}
And the new command would be the same but adjusting the location to use this new folder:
docker run -d \
--name stirling-pdf \
-p 8080:8080 \
-v "/home/admin/Desktop/StirlingPDF/trainingData:/usr/share/tessdata" \
-v "/home/admin/Desktop/StirlingPDF/extraConfigs:/configs" \
-v "/home/admin/Desktop/StirlingPDF/customFiles:/customFiles/" \
-v "/home/admin/Desktop/StirlingPDF/logs:/logs/" \
-v "/home/admin/Desktop/StirlingPDF/pipeline:/pipeline/" \
-e DOCKER_ENABLE_SECURITY=false \
-e LANGS=en_GB \
stirlingtools/stirling-pdf:latest
It seems that the only hackers that I'm tripping up here are the ones that are trying to help me!
Should it try these stops from the original administrator account? (User10)
Would that make a difference?
No, the whole point of Docker containers is that they can run programs in isolation. Involving another user account only makes things more complicated.
It seems that it takes a while to initialize the whole application after the Docker container starts. According to your logs it should be only a few seconds, but maybe give it some more time before trying to connect.
By the way, have you already try to disable the VPN? That seems to be the only thing left to try at this point.
You can also run a quick test through the terminal:
curl -I localhost:8080
If it's working it should return a 200 status code. Which would point to an issue with the browsers for some reason.
