anonym.legal

By · Last updated 2026-08-12

Bahay/Dokumentasyon/breadcrumb.nextcloud/Pag-aayos ng Problema

Pag-aayos ng Problema & FAQ

Ayusin karaniwang problema sa anonym.legal Nextcloud: pagtanggi SSRF host allowlist, notice bagong bersyon, error Basic-plan gating mula dalawang app.

Tinanggihan ang backend API URL (SSRF allowlist)

Tumatanggi ang app na i-save ang backend API URL, o nabibigo ang mga kahilingan na may URL-not-allowed error.

Bakit ito nangyayari

Sinusuri ng parehong app ang na-configure na backend API URL laban sa runtime-validated host allowlist (UrlGuard) bago gumawa ng anumang kahilingan. Umiiral ang SSRF guard na ito upang hindi kailanman maabot ng Bearer token ng app ang host na kontrolado ng attacker dahil sa isang malisyoso o maling na-configure na URL. Anonym.legal at anonymize.business (ang DEV host) lamang ang pinapayagan — tinatanggihan ang lahat ng ibang host, ayon sa disenyo.

Paano ayusin

  1. 1.Gamitin nang eksakto ang https://anonym.legal (production) o https://anonymize.business (DEV) bilang backend API URL.
  2. 2.Alisin ang anumang trailing path, port, o typo mula sa URL — eksaktong tinutugma ng allowlist ang hostname.
  3. 3.Kung naniniwala kang isang lehitimong host ang tinatanggihan, makipag-ugnayan sa support — sadyang hindi na-e-edit ng user ang allowlist.

Ang notice na "May available na bagong bersyon"

Ipinapakita ng admin settings ng app ang notice na may bagong bersyong umiiral.

Bakit ito nangyayari

Parehong regular na sinusuri ng dalawang app kung may mas bagong bersyon at nagpapakita ng simpleng admin notice na may link sa changelog kapag mayroong available. Ito ay isang manual-upgrade notice, hindi isang awtomatikong update — walang nag-i-install sa sarili nito sa iyong Nextcloud instance.

Paano ayusin

  1. 1.Sundan ang changelog link sa notice upang suriin kung ano ang nagbago.
  2. 2.I-download ang bagong app archive(s) mula sa GitHub releases page.
  3. 3.I-extract sa apps/ at patakbuhin ang occ upgrade — ang parehong manual install steps ng unang pag-install — sa iyong sariling schedule.

403 error: "Basic plan o mas mataas"

Nabibigo ang mga API call mula sa app na may 403 status at mensahe tungkol sa pangangailangan ng Basic plan o mas mataas.

Bakit ito nangyayari

Ang dalawang Nextcloud app ay nangangailangan ng anonym.legal account sa Basic plan o mas mataas. Hindi kasama sa free plan ang API access na inaasahan ng mga app na ito, kaya ibinabalik ng backend ang 403 kasama ang mensahe na "Nextcloud integration requires Basic plan or higher. Please upgrade your plan." sa halip na tahimik na pagkabigo.

Paano ayusin

  1. 1.Kumpirmahin kung aling anonym.legal account ang pagmamay-ari ng na-configure na token.
  2. 2.I-upgrade ang account na iyon sa Basic plan o mas mataas.
  3. 3.Ulitin ang kahilingan — walang kailangang i-reinstall o i-reconfigure kapag na-upgrade na ang account.

Hindi mabasa ng integration token ang encryption keys — bug ba ito?

Tinatanggihan ang kahilingang sumusubok na kunin ang decrypted key material gamit ang na-configure na token.

Bakit ito nangyayari

Hindi — ito ay sinasadya. Ang token na ginagamit ng mga app na ito ay isang integration-scoped token, na sadyang mas limitado kaysa sa buong-account na API token: maaari nitong i-analyze at i-anonymize ang content, ngunit ang bawat endpoint na magbabalik ng decrypted key material ay nagbibigay ng 403 sa integration-scoped token, kaya hindi kailanman magagamit ang na-compromise na Nextcloud server upang i-decrypt ang iyong reversible-encryption history.

Ano ang dapat gawin

  1. 1.Ito ang inaasahang pag-uugali, hindi isang error na kailangang ayusin — hindi kailanman kailangan ng mga app ang decrypted key material para sa kanilang analyze/anonymize/deanonymize workflow.
  2. 2.Kung talagang kailangan ng isang workflow ang buong-account na access, gumamit ng full-scope API token sa labas ng mga app na ito, sa isang context na iyong kontrolado.

Kailangan Pa Rin ng Tulong?

Kung wala sa mga solusyon sa itaas ang gumana, makipag-ugnayan sa amin at tutulungan ka naming ayusin ang isyu.

Bumalik sa Nextcloud Docs

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

Related reading

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022, held by our hosting provider.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our company HQ is in Saarbrücken, Germany. Our servers run in Hetzner's Falkenstein datacenter.

Hetzner holds ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

Automated checks run on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We test detection against sample documents before each release.

A failing unit or integration run stops the release.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

Paid plans can buy top-up credits.

Credits reset at the end of each cycle.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.