honoki / bbrf-server Goto Github PK

[notice] 2022-04-19T02:21:58.403323Z nonode@nohost <0.316.0> -------- chttpd_auth_cache changes listener died because the _users database does not exist. Create the database to silence this notice.
[error] 2022-04-19T02:21:58.404076Z nonode@nohost emulator -------- Error in process <0.904.0> with exit value:
{database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,399}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,374}]},{mem3_shards,load_shards_from_disk,2,[{file,"src/mem3_shards.erl"},{line,403}]},{mem3_shards,for_docid,3,[{file,"src/mem3_shards.erl"},{line,96}]},{fabric_doc_open,go,3,[{file,"src/fabric_doc_open.erl"},{line,39}]},{chttpd_auth_cache,ensure_auth_ddoc_exists,2,[{file,"src/chttpd_auth_cache.erl"},{line,198}]},{chttpd_auth_cache,listen_for_changes,1,[{file,"src/chttpd_auth_cache.erl"},{line,145}]}]}

Hello devs,
my bbrf listener keeps giving this timeout error after few minutes

bbrf listner &

[ERROR] HTTPSConnectionPool(host='72.XX.XX.XX', port=443): Read timed out. (read timeout=90)

I have tried running the bbrf listener in bot background and a separate tmux session as well.

Hi,

how can I backu[ database to server when I use docker?

Can you please update the Dockerhub image

[notice] nonode@nohost <0.316.0> -------- chttpd_auth_cache changes listener died because the _users database does not exist. 
Create the database to silence this notice.

[error] nonode@nohost emulator -------- Error in process <0.3589.0> with exit value:

{database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,399}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,374}]},{mem3_shards,load_shards_from_disk,2,[{file,"src/mem3_shards.erl"},{line,403}]},{mem3_shards,for_docid,3,[{file,"src/mem3_shards.erl"},{line,96}]},{fabric_doc_open,go,3,[{file,"src/fabric_doc_open.erl"},{line,39}]},{chttpd_auth_cache,ensure_auth_ddoc_exists,2,[{file,"src/chttpd_auth_cache.erl"},{line,198}]},{chttpd_auth_cache,listen_for_changes,1,[{file,"src/chttpd_auth_cache.erl"},{line,145}]}]}

I have a doubt , is bbrf-server support heroku instead of AWS?

If it possible can any one share how to do that?

cat ~/.bbrf/config.json | grep "ignore_ssl_errors"

"ignore_ssl_errors": true

docker-compose logs proxy

proxy_1 | 2022/08/30 19:35:29 [emerg] 1#1: cannot load certificate "/etc/nginx/keys/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/nginx/keys/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
proxy_1 | nginx: [emerg] cannot load certificate "/etc/nginx/keys/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/nginx/keys/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)

bbrf new myprogram

[ERROR] HTTPSConnectionPool(host='', port=443): Max retries exceeded with url: /bbrf/ (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f3cddc237b8>: Failed to establish a new connection: [Errno 111] Connection refused',))

docker-compose ps

    Name                       Command               State               Ports            

bbrf-server_couchdb_1 tini -- /docker-entrypoint ... Up 4369/tcp, 5984/tcp, 9100/tcp
bbrf-server_proxy_1 nginx -g daemon off; Exit 1

Hi,

I am using an AWS Lightsail machine to host this server. The book did everything, DNS, Certbot, passed change.

Docker-compose up -d ends without any error.

However, no TCP 443 is opened to continue the setup.

docker ps
CONTAINER ID   IMAGE                COMMAND                  CREATED         STATUS         PORTS                          NAMES
0980f0f12db4   honoki/bbrf-server   "tini -- /docker-ent…"   7 minutes ago   Up 7 minutes   4369/tcp, 5984/tcp, 9100/tcp   bbrf-server-couchdb-1

Any ideas on how to debug this?

Thanks!

Hello Devs,
I am trying to setup the bbrf server on my Lionde VPS (debian 11). When running the command docker-compose up -d, I get the following error

root@localhost:~/bbrf-server# docker-compose up -d 
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.

Can you tell why it is so, do I need to manually change the version in compose file ?

Thanks and Regards,

{
"username": "admin",
"password": "password",
"couchdb": "https://127.0.0.1/_utils/#database/bbrf/_all_docs/bbrf",
"slack_token": "",
"discord_webhook": "",
"ignore_ssl_errors": "true"
}

bbrf new google

the resault

[ERROR] BBRF server error: method_not_allowed

While removing or adding a big amount of domains/urls (over 100k) I'm getting the error unknown_error

This is the error from the CouchDB Log.

[error] 2021-04-27T23:54:43.969434Z [email protected] <0.27214.75> 5fba4475ec req_err(492424286) unknown_error : badarg

Sometimes all urls/domains are deleted any ways, sometimes there's some left over, running the command again removes all documents.