Posts made by necrevistonnezr

BTW: There are now official docker-compose scripts: https://git.tt-rss.org/fox/ttrss-docker-compose

Stupid me! My docker repository was set to private!
Once made public - at least for the time of updating - a simple click on "repair" in the Cloudron control panel was enough!

Thanks for the hint. In the control panel, I have the following error:

An error occurred during the operation: Docker Error: Unable to pull image. Please check the network or if the image needs authentication. statusCode: 404

Output of cloudron build:

Building locally as necrevistonnezr/bitwardenrs:20191210-094936-34576695f

Sending build context to Docker daemon  114.2kB

Step 1/28 : FROM "bitwardenrs/server:1.13.0-alpine" as bitwarden
 ---> c0f785714c65
Step 2/28 : FROM cloudron/base:1.0.0@sha256:147a648a068a2e746644746bbfb42eb7a50d682437cead3c67c933c546357617
 ---> 534bd0efda10
Step 3/28 : ENV ROCKET_ENV "staging"
 ---> Using cache
 ---> 08e348a2d671
Step 4/28 : ENV ROCKET_PORT=3000
 ---> Using cache
 ---> 4f829684eb90
Step 5/28 : ENV ROCKET_WORKERS=10
 ---> Using cache
 ---> 4c341fbb8b34
Step 6/28 : ENV DATA_FOLDER=/app/data
 ---> Using cache
 ---> 624de75507eb
Step 7/28 : ENV CONFIG_FILE=/app/data/config.json
 ---> Using cache
 ---> df63ce28a824
Step 8/28 : ENV SIGNUPS_ALLOWED=false
 ---> Using cache
 ---> 98489eda2ecf
Step 9/28 : ENV INVITATIONS_ALLOWED=true
 ---> Using cache
 ---> 363bd3b89949
Step 10/28 : ENV WEBSOCKET_ENABLED=true
 ---> Using cache
 ---> c3ab1f3b150c
Step 11/28 : ENV DISABLE_ADMIN_TOKEN=true
 ---> Using cache
 ---> 57d590406e2c
Step 12/28 : RUN mkdir -p /app/data
 ---> Using cache
 ---> bf796d6b68b4
Step 13/28 : VOLUME /app/data
 ---> Using cache
 ---> af0388a6c7c5
Step 14/28 : EXPOSE 80
 ---> Using cache
 ---> c4e5fc4eef9c
Step 15/28 : EXPOSE 3012
 ---> Using cache
 ---> 0d3be2006979
Step 16/28 : RUN rm /etc/apache2/sites-enabled/*
 ---> Using cache
 ---> 128658526e5f
Step 17/28 : RUN sed -e 's,^ErrorLog.*,ErrorLog "|/bin/cat",' -i /etc/apache2/apache2.conf
 ---> Using cache
 ---> 460b63a85e66
Step 18/28 : RUN a2disconf other-vhosts-access-log
 ---> Using cache
 ---> b660416c4b47
Step 19/28 : COPY apache.conf /etc/apache2/sites-enabled/bitwarden.conf
 ---> Using cache
 ---> 380066c29b0c
Step 20/28 : RUN a2enmod ldap authnz_ldap proxy proxy_http proxy_wstunnel rewrite
 ---> Using cache
 ---> 5d85bcdb4449
Step 21/28 : COPY --from=bitwarden /web-vault /app/code/web-vault
 ---> Using cache
 ---> 8c8e6cd0a79a
Step 22/28 : COPY --from=bitwarden /bitwarden_rs /app/code/
 ---> Using cache
 ---> 23aa34133bc8
Step 23/28 : COPY --from=bitwarden /Rocket.toml /app/code/
 ---> Using cache
 ---> 16d854c4cdb4
Step 24/28 : ADD supervisor/ /etc/supervisor/conf.d/
 ---> Using cache
 ---> 94e6be8b3e39
Step 25/28 : RUN sed -e 's,^logfile=.*$,logfile=/run/supervisord.log,' -i /etc/supervisor/supervisord.conf
 ---> Using cache
 ---> a4b630549d9e
Step 26/28 : WORKDIR /app/code
 ---> Using cache
 ---> ac66a3410991
Step 27/28 : COPY start.sh /app/code/start.sh
 ---> Using cache
 ---> 8fee6c91fd4a
Step 28/28 : CMD [ "/app/code/start.sh" ]
 ---> Using cache
 ---> ebd0cc6480c9
Successfully built ebd0cc6480c9
Successfully tagged necrevistonnezr/bitwardenrs:20191210-094936-34576695f

Pushing necrevistonnezr/bitwardenrs:20191210-094936-34576695f
The push refers to repository [docker.io/necrevistonnezr/bitwardenrs]
59ca39a8baf6: Preparing
d20566396bfd: Preparing
426f40b89686: Preparing
351495e80404: Preparing
205c5dee79e1: Preparing
4f9345d26f82: Preparing
ffd05eeb91b1: Preparing
5418b55c5d1d: Preparing
92cad9313b91: Preparing
0ea137c0c63c: Preparing
16ef7d4b2f8e: Preparing
f8a2b79c8722: Preparing
5648d21d9467: Preparing
bfe34f2cfbd0: Preparing
83a42f6af455: Preparing
f81e4eb4d80a: Preparing
cd78fba29389: Preparing
5662a07238a1: Preparing
8d7ea83e3c62: Preparing
6a061ee02432: Preparing
f73b2816c52a: Preparing
6267b420796f: Preparing
a30b835850bf: Preparing
5648d21d9467: Waiting
bfe34f2cfbd0: Waiting
83a42f6af455: Waiting
f81e4eb4d80a: Waiting
cd78fba29389: Waiting
4f9345d26f82: Waiting
5662a07238a1: Waiting
8d7ea83e3c62: Waiting
6a061ee02432: Waiting
ffd05eeb91b1: Waiting
5418b55c5d1d: Waiting
f73b2816c52a: Waiting
6267b420796f: Waiting
92cad9313b91: Waiting
0ea137c0c63c: Waiting
16ef7d4b2f8e: Waiting
f8a2b79c8722: Waiting
a30b835850bf: Waiting
351495e80404: Layer already exists
205c5dee79e1: Layer already exists
d20566396bfd: Layer already exists
426f40b89686: Layer already exists
59ca39a8baf6: Layer already exists
4f9345d26f82: Layer already exists
ffd05eeb91b1: Layer already exists
0ea137c0c63c: Layer already exists
16ef7d4b2f8e: Layer already exists
f8a2b79c8722: Layer already exists
92cad9313b91: Layer already exists
5418b55c5d1d: Layer already exists
5648d21d9467: Layer already exists
bfe34f2cfbd0: Layer already exists
f81e4eb4d80a: Layer already exists
5662a07238a1: Layer already exists
cd78fba29389: Layer already exists
8d7ea83e3c62: Layer already exists
83a42f6af455: Layer already exists
6a061ee02432: Layer already exists
f73b2816c52a: Layer already exists
6267b420796f: Layer already exists
a30b835850bf: Layer already exists
20191210-094936-34576695f: digest: sha256:ab443082901c6beac8d3e222448e20436b5e4d51c380bc2146f1f8d868ce06d4 size: 5114

And how do I get past the 409 message: Not allowed in error state?

In all fairness - the first post is just an opportunity to post OP's ref code for Digitalocean IMHO

Still gettin errors:

osboxes@osboxes:~/bitwardenrs-app$ cloudron update --app bit
Will update app at location bit
 => Waiting for app to be updated 
 => Starting ... ...
 => Backup - Snapshotting app bit.mydomain.de ..
 => Backup - undefined 
 => Downloading image ...........................................
App update error: Installation failed: undefined

osboxes@osboxes:~/bitwardenrs-app$ sudo cloudron update --app bit
Will update app at location bit
Failed to update app: 409 message: Not allowed in error state

@fbartels said in Bitwarden - Self-hosted password manager:

@murgero said in Bitwarden - Self-hosted password manager:

This requires the build service app to be installed on your cloudron

That is not true. Its build locally and then pushed into the github account.

When I try to update my bitwarden app at the existing domain 'bit.mydomain.de' this way, I still get a

Failed to install app: 409 message: Domain 'bit.mydomain.de' is in use

I have a wildcard DNS entry), so a DNS entry for the subdomain should not cause trouble. I also tried cloudron login --allow-selfsigned but it doesn't change anything.

Could the "version" entry in CloudronManifest.jsonbe the culprit?

There will be no more periodic tags for TT-RSS. Git Master is the only supported version. Maybe it's time again to think about a rolling release for this app? And switch to PostgreSQL as recommended by the Author while you're at it?

https://community.tt-rss.org/t/versioning-changes-for-trunk/2974/

I’m tired of people (this means package and container maintainers, not end-users) who stay on tt-rss tags instead of git master for whatever reason.
Therefore,

• Don’t expect any more periodic tags, ever. Prepare to stay in August 2019 forever if you’re using that particularly terrible “linuxserver” container.
• Static version prefix is no longer going to be a thing. Your either run off git and get correct timestamp and commit you’re on (because this information is actually useful to help you in case something is broken), or you get “Unknown (unsupported)” because, as far as I’m concerned, that’s what you’re running.
• As before, only latest code off git master is supported. If you’re running anything else, update before reporting any issues.

@nebulon there is a deb package at https://github.com/ONLYOFFICE/DesktopEditors/releases/tag/ONLYOFFICE-DesktopEditors-5.4.2 (?)

5.4.2 is out
https://github.com/ONLYOFFICE/DesktopEditors/releases/tag/ONLYOFFICE-DesktopEditors-5.4.2

@nebulon I don't remember this link being there (that you removed) when this topic was opened a few months ago... Otherwise I'm sure someone or me would have reported it.

Caveat: Tiny Tiny RSS switches to app specifice passwords

https://community.tt-rss.org/t/upcoming-authentication-changes-in-trunk/2850:

Some changes are coming regarding API and TOTP.

• I’m planning to implement app-specific passwords, for the time being used only for API clients (i.e. android/ios apps and whatever else);
• Unless you’re using OTP, you will be able to continue using your regular password in the client application or create an app-specific one, both would work;
• If you’re using OTP, your regular password will not be accepted. You will need to create an app-specific password[1] to continue using your API client application.
  Go to Preferences → Authentication → App passwords

Nope, as the Cloudron App is based on Apache (there was already a thread on this a couple of days ago, can’t find it...)

Fulltext Search for Nextcloud would be awesome!

Filesystem                  Type      Size  Used Avail Use% Mounted on
udev                        devtmpfs  3.8G     0  3.8G   0% /dev
tmpfs                       tmpfs     765M  2.9M  762M   1% /run
/dev/mapper/beebox--vg-root ext4      455G  299G  133G  70% /
tmpfs                       tmpfs     3.8G  8.0K  3.8G   1% /dev/shm
tmpfs                       tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs                       tmpfs     3.8G     0  3.8G   0% /sys/fs/cgroup
/dev/loop1                  squashfs  8.5M  8.5M     0 100% /snap/canonical-livepatch/81
/dev/loop3                  squashfs   90M   90M     0 100% /snap/core/7713
/dev/sdb1                   ext2      472M  144M  304M  33% /boot
/dev/sda1                   ext4      1.8T  1.5T  261G  86% /media/SG2TB
/dev/loop4                  squashfs  8.7M  8.7M     0 100% /snap/canonical-livepatch/84
/dev/loop2                  squashfs   90M   90M     0 100% /snap/core/7917

I have one SSD and one HDD in my homeserver running Cloudron 4.2.6 - neither are shown in "Graphs"...

The output of df -h:

Filesystem                   Size  Used Avail Use% Mounted on
udev                         3.8G     0  3.8G   0% /dev
tmpfs                        765M  2.8M  763M   1% /run
/dev/mapper/beebox--vg-root  455G  299G  133G  70% /
tmpfs                        3.8G  8.0K  3.8G   1% /dev/shm
tmpfs                        5.0M     0  5.0M   0% /run/lock
tmpfs                        3.8G     0  3.8G   0% /sys/fs/cgroup
/dev/loop1                   8.5M  8.5M     0 100% /snap/canonical-livepatch/81
/dev/loop3                    90M   90M     0 100% /snap/core/7713
/dev/sdb1                    472M  144M  304M  33% /boot
/dev/sda1                    1.8T  1.5T  259G  86% /media/SG2TB
/dev/loop4                   8.7M  8.7M     0 100% /snap/canonical-livepatch/84
/dev/loop2                    90M   90M     0 100% /snap/core/7917

@girish that gives me the same error but pinging works

bitwardenrs-app on master [!?] via ⬢ v12.7.0
➜ cloudron login my.cloudron.io
ERROR (node:55034) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification. [ internal/process/warning.js:27:3 ]
ERROR Cloudron my.cloudron.io not found.
Try providing the admin location, probably my.my.cloudron.io [ /Users/kdj/.nvm/versions/node/v12.7.0/lib/node_modules/cloudron/src/helper.js:71:29 ]
bitwardenrs-app on master [!?] via ⬢ v12.7.0 took 18s
➜ ping my.cloudron.io
PING my.cloudron.io (45.55.2.141): 56 data bytes
64 bytes from 45.55.2.141: icmp_seq=0 ttl=50 time=188.063 ms
64 bytes from 45.55.2.141: icmp_seq=1 ttl=50 time=181.041 ms
64 bytes from 45.55.2.141: icmp_seq=2 ttl=50 time=237.531 ms

@girish Yes, the situation is the same with or without "--allow-selfsigned"
BTW I'm on macOS 10.15

Again, there's trouble with cloudron cli. I tried to login but it gives me the following errors:

cloudron login --allow-selfsigned
Cloudron Admin Domain: my.domain.com
ERROR (node:51749) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification. [ internal/process/warning.js:27:3 ]
ERROR Cloudron my.domain.com not found.
Try providing the admin location, probably my.my.domain.com [ /Users/user/.nvm/versions/node/v12.7.0/lib/node_modules/cloudron/src/helper.js:71:29 ]

What am I doing wrong?