anonym.legal

By · Last updated 2026-08-12

Nyumbani/Dokumentasyonu/breadcrumb.nextcloud/Utatuzi wa Matatizo

Utatuzi wa Matatizo na Maswali Yanayoulizwa Mara kwa Mara

Rekebisha matatizo ya Nextcloud ya anonym.legal: kukataliwa kwa orodha ruhusiwa ya wenyeji SSRF, arifa ya toleo jipya, na makosa ya mpango Basic wa apps

URL ya API ya nyuma imekataliwa (orodha ya wenyeji ruhusiwa ya SSRF)

Programu inakataa kuhifadhi URL ya API ya nyuma, au maombi hushindwa kwa kosa la URL-isiyoruhusiwa.

Kwa nini hii hutokea

Programu zote mbili huthibitisha URL ya API ya nyuma iliyosanidiwa dhidi ya orodha ya wenyeji ruhusiwa iliyothibitishwa wakati wa uendeshaji (UrlGuard) kabla ya kufanya ombi lolote. Ulinzi huu wa SSRF upo ili URL yenye nia mbaya au iliyosanidiwa vibaya isiweze kamwe kusababisha funguo ya Bearer ya programu kufikia mwenyeji unaodhibitiwa na mshambuliaji. Ni anonym.legal na anonymize.business (mwenyeji wa DEV) pekee wanaoruhusiwa — mwenyeji mwingine yeyote hukataliwa, kwa makusudi.

Jinsi ya kurekebisha

  1. 1.Tumia hasa https://anonym.legal (uzalishaji) au https://anonymize.business (DEV) kama URL ya API ya nyuma.
  2. 2.Ondoa njia yoyote ya mwisho, bandari, au kosa la kuandika kutoka URL — orodha ya wenyeji ruhusiwa hulinganisha jina la mwenyeji kwa usahihi.
  3. 3.Ikiwa unaamini mwenyeji halali anakataliwa, wasiliana na msaada — orodha ya wenyeji ruhusiwa kwa makusudi haiwezi kuhaririwa na mtumiaji.

Arifa ya "Toleo jipya linapatikana"

Mipangilio ya msimamizi ya programu huonyesha arifa kuwa toleo jipya zaidi lipo.

Kwa nini hii hutokea

Programu zote mbili hukagua mara kwa mara kama toleo jipya zaidi lipo na kuonyesha arifa rahisi ya msimamizi yenye kiungo cha orodha ya mabadiliko toleo linapopatikana. Hii ni arifa ya kuboresha kwa mkono, si sasisho la kiotomatiki — hakuna kinachojisakinisha kwenye kifaa chako cha Nextcloud.

Jinsi ya kurekebisha

  1. 1.Fuata kiungo cha orodha ya mabadiliko katika arifa ili kukagua kilichobadilika.
  2. 2.Pakua kumbukumbu mpya za programu kutoka ukurasa wa GitHub releases.
  3. 3.Toa kwenye apps/ na uendeshe occ upgrade — hatua zile zile za mkono za usakinishaji kama usakinishaji wa awali — kwa ratiba yako mwenyewe.

Kosa la 403: "Mpango wa Basic au zaidi"

Wito za API kutoka kwa programu hushindwa kwa hali ya 403 na ujumbe kuhusu kuhitajika kwa mpango wa Basic au zaidi.

Kwa nini hii hutokea

Programu zote mbili za Nextcloud zinahitaji akaunti ya anonym.legal kwenye mpango wa Basic au zaidi. Mpango wa bure hauhusishi ufikiaji wa API ambao programu hizi hutegemea, hivyo mfumo wa nyuma hurejesha 403 na ujumbe "Nextcloud integration requires Basic plan or higher. Please upgrade your plan." badala ya kushindwa kimya.

Jinsi ya kurekebisha

  1. 1.Thibitisha akaunti gani ya anonym.legal funguo iliyosanidiwa inayohusiana nayo.
  2. 2.Boresha akaunti hiyo kwenye mpango wa Basic au zaidi.
  3. 3.Jaribu ombi tena — hakuna usakinishaji upya au usanidi upya unaohitajika mara akaunti inapoboreshwa.

Funguo ya ujumuishaji haiwezi kusoma funguo za usimbaji fiche — je, hilo ni kosa?

Ombi linalojaribu kupata nyenzo za funguo zilizosimbwa fiche kwa funguo iliyosanidiwa hukataliwa.

Kwa nini hii hutokea

Hapana — hii ni kwa makusudi. Funguo inayotumiwa na programu hizi ni funguo yenye wigo mdogo kwa ajili ya ujumuishaji, kwa makusudi ina mipaka zaidi kuliko funguo kamili ya API ya akaunti: inaweza kuchambua na kuanonimisha maudhui, lakini sehemu ya mwisho yoyote ambayo ingerejesha nyenzo za funguo zilizosimbwa fiche hurejesha 403 kwa funguo yenye wigo mdogo kwa ajili ya ujumuishaji, hivyo seva ya Nextcloud iliyoathiriwa haiwezi kamwe kutumika kufungua usimbaji fiche wa historia yako ya usimbaji unaoweza kutenduliwa.

Nini cha kufanya

  1. 1.Hili ni tabia inayotarajiwa, si kosa la kurekebisha — programu hazihitaji kamwe nyenzo za funguo zilizosimbwa fiche kwa mtiririko wao wa kazi wa kuchambua/kuanonimisha/kuondoa uanonimishaji.
  2. 2.Iwapo mtiririko wa kazi kwa kweli unahitaji ufikiaji kamili wa akaunti, tumia funguo ya API yenye wigo kamili nje ya programu hizi, katika mazingira unayodhibiti.

Bado Unahitaji Msaada?

Ikiwa hakuna suluhisho lolote kati ya haya lililofanya kazi, wasiliana nasi na tutakusaidia kutatua tatizo.

Rudi kwenye Nyaraka za Nextcloud

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.