RazorHail's questions

I've set up a Docker Registry (port 5000), which is then accessible to the internet via Reverse-Proxy (HAproxy) via https (port 443).

My reverse-proxy isn't listening on port 80 (for various reasons) - only 443.

However, when I try to pull/push images to the registry, I get this error:

> docker push dockerreg.mydomain.tld/foo/bar:tag
The push refers to repository [dockerreg.mydomain.tld/foo/bar]
67e5bc702bd3: Layer already exists
1ee6a18298af: Layer already exists
0d8d066a4449: Layer already exists
....
402111a9b517: Layer already exists
5be968ab3b04: Layer already exists
b8d33b7d28fe: Layer already exists
Patch http://dockerreg.mydomain.tld/v2/foo/bar/blobs/uploads/840a9fc2-5c10-4c0e-b674-82f76c3794a3?_state=vcTZPbOrQmhcKwilCyutNGwVpFjvWigJCApZHA834757Ik5hbWUiOiJmb3Rvd2V0dGVyL2NsZWFuIiwiVVVJRCI6Ijg0MGE5ZmMyLTVjMTAtNGMwZS1iNjc0LTgyZjc2YzM3OTRhMyIsIk9mZnNldCI6MCwiU3RhcnRlZEF0IjoiMjAyMS0wOC0xNFQyMTozODo1Mi42MzgxNjY5NTdaIn0%3D:
dial tcp 1.2.3.4:80: i/o timeout

So apparently it tries to access the registry via http/80

I was able to use the docker login command with https://dockerreg.... but the docker pull/push commands can't be run with a https://

Is there any way to access my docker registry without a https-redirect on port 80 of my reverse-proxy?

I'm running Snapraid on my hard drives. However, I want to test it's data integrity features, to see how/if they actually work.

But I don't really understand how to 'corrupt' my data. I can just manually change the contents of my files. However, Snapraid will just sync this change normally. And Snapraid fix will automatically revert the files to before the change.

But how do I test an actual data corruption, and how do I know if Snapraid has actually fixed it?

I'm running a debian-server with OpenVPN and I'm trying to establish a connection to it over the internet (windows client). However I've noticed that it always takes a long time, since it seems to hit the timeout.

I always get to this part:

MANAGEMENT: >STATE:1561445206,WAIT

at the end of the timeout, I get this:

TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
TLS Error: TLS handshake failed

HOWEVER, then my client tries to connect again (after 5 seconds) and it immediately establishes the connection.

SIGUSR1[soft,tls-error] received, process restarting
MANAGEMENT: >STATE:1561445266,RECONNECTING,tls-error,,,,,
Restart pause, 5 second(s)
TCP/UDP: Preserving recently used remote address: [AF_INET]x.x.x.x:x
Socket Buffers: R=[65536->65536] S=[65536->65536]
UDP link local: (not bound)
UDP link remote: [AF_INET]x.x.x.x:x
MANAGEMENT: >STATE:1561445271,WAIT,,,,,,
MANAGEMENT: >STATE:1561445271,AUTH,,,,,,

90% of the time it works like this where it only connects on the second try - sometimes it also (seemingly at random) connects on the first try

I have a CVS-repository, which should be continued to be used for old projects (commits, etc. should be allowed).

However, I want to disable the creation of new repositories.

First thing I tried, was to set the root-CVS-folder to read-only, but now CVS doesn't work at all, because it needs to create a lock-file in the root-folder (which he can't do anymore, because it's read-only)

My (free) webhoster allows me to run ONE cronjob (through their web interface). But I need to run Two. One cronjob every 10 minutes, and another one every Hour.

They're both PHP-files. Is there a way to just have one job (that runs every 10 minutes) that executes the 10-minute-job and then also executes the hour-job every 6 runs?

Screenshot of the Hoster's Web interface

I'm trying to schedule a command to run only once with at. But the server is prone to reboot at least once every day.

I already tried to schedule a command with at` to be executed in 24 hours, but it wasn't executed.

how can I get at to remember the scheduled task, even after the reboot?

I have a debian-squeeze host-system on which I have installed lxc.

i created a (squeeze) container, and started it. then I'm trying to get inside the container with lxc-console. everything works fine so far.

but the weird thing is, lxc-console only works once! meaning: if detach from it (Ctrl+a q) and try to reattach again (lxc-console -n containername) the command prompt never appears. it just says "Type Ctrl+a q to exit the console" but that's it. nothing else - no login prompt

I can exit the console and try to reconnect - but still the same.

the only way to get it to work again is, stopping the container and restarting it again. then I can connect via lxc-console. but again....only ONCE. after the disconnect, I don't see a command prompt anymore....

has anybody seen this kind of behavior before?