bravemonkey

joined 2 years ago
[–] bravemonkey@lemmy.ca 2 points 1 week ago (1 children)

Shorthand is hard to learn from and hard to troubleshoot in complicated scripts.

[–] bravemonkey@lemmy.ca 4 points 1 month ago* (last edited 1 month ago)

From the Windows side (assuming you're using Windows to connect, considering it's RDP and not VNC), you can open PowerShell and test to see if the Raspberry Pi is even listening for RDP connections with:

Test-NetConnection x.x.x.x -port 3389

Replace x.x.x.x with the IP address of the Raspberry Pi. If it shows successful, then the Raspberry Pi is listening for RDP connections.

Do you know what RDP package you installed, and what operating system you're running (Bookworm, Bullseye, etc)? I don't have a raspberry pi with a desktop to test on, but if you're using xrdp you could try:

sudo systemctl status xrdp

Does this give any input? If not, then you'll need to know what package you installed to get RDP, assuming one is still installed even. If it does give you a message it might be a hint as to why it's not working.

If you get output from the above command you can also try:

sudo journalctl -b | grep -C 2 xrdp

There are much better ways of searching journalctl but I'm a noob too. The -b returns only errors from the last boot time, the -C returns that many lines before and after a match is found.

[–] bravemonkey@lemmy.ca 1 points 1 month ago

So that means the router isn't forwarding the ports to your devices. As others have said, it could be the ISP blocking it or it could be a configuration issue in the port fowarding.

[–] bravemonkey@lemmy.ca 2 points 1 month ago (2 children)

Do you have any service listening on port 80? If not, I'd close it in the firewall and disable the forwarding in the router. Also sounds like a bad idea to set your router security to 'low', whatever that means for your router.

You can use a tool like this to check if your ports are accessible from the internet: https://www.yougetsignal.com/tools/open-ports/

[–] bravemonkey@lemmy.ca 1 points 1 month ago

Sorry, what’s preventing you from adding the subdomains in the Vultr DNS?

[–] bravemonkey@lemmy.ca 6 points 2 months ago (10 children)

For me it’s that Tumblweed at least uses BTRFS by default, so rolling back to a previous snapshot is a breeze if needed.

[–] bravemonkey@lemmy.ca 5 points 3 months ago

Yes, that's very different than the 'pressing your thumb' like you said in the message I was replying to.

[–] bravemonkey@lemmy.ca 6 points 3 months ago (2 children)

Carving letters into the wood equals ‘pressing his thumb’ to you? Did you even read the article? Regardless, let me ‘press my thumb’ into your forehead and see if you think it’s fine, just let me be.

[–] bravemonkey@lemmy.ca 27 points 3 months ago* (last edited 3 months ago) (7 children)

I tipped him well

I can’t tell if that’s supposed to be sarcasm, but if not you were encouraging his bad behaviour.

[–] bravemonkey@lemmy.ca 4 points 3 months ago

I'm happy for them to be posted here and see them, just wanted to mention my experience with the requirements since I don't have a fanatical account.

[–] bravemonkey@lemmy.ca 5 points 3 months ago (2 children)

It's not just 'sign up for a newsletter' - I just tried, and it's also 'register an account and link your steam account'. Maybe this is just how it works for Canadians though, but either way it's a big enough turn off for me to not bother.

 

I'm new to Podman and so far have been completely frustrated by it.
I don't know if the issue is with the container or Podman since there are just no logs.

I'm trying to run Stirling-PDF, using this command:

podman run -d
-p 8080:8080
-v /location/of/trainingData:/usr/share/tesseract-ocr/5/tessdata
-v /location/of/extraConfigs:/configs
-v /location/of/logs:/logs
-e DOCKER_ENABLE_SECURITY=false
--name stirling-pdf
frooodle/s-pdf:latest

With Docker, I have no issue running the this container. Under Podman the container immediately exits without logs - podman logs stirling-pdf shows nothing.

The same thing happens running the same command with sudo or without sudo but using --rootful. I've also tried removing '-e DOCKER_ENABLE_SECURITY=false ' since it's very Docker specific.

I can run podman run -dt --name webserver -p 8081:80 quay.io/libpod/banner with no issues, so is this something incompatible with the container?

I feel like I'm missing something obvious - like where are the logs?

I'm running on OpenSUSE-Tumbleweed, Podman version 4.9.0

view more: next ›