Files
wireguard_webadmin/locale/pt_BR/LC_MESSAGES/django.mo
T

568 lines
122 KiB
Modelica
Raw Normal View History

2026-11-20 21:58:17 -03:00
ή•΅$α,:°M½±MΆoPSTmfVΤYήνZ~Μ\‚K]wΞ]F^3d_ƒ�`xf•f�§hωBiρ<j.m�JpΦυu\Μw�){lΈ}&%‚L…Ii†­³�~a�Oΰ•30–Fd–:«—]ζ—/D�+t�' �Θ�Ο�α���™ $™
.™<™L™#\™!€™Ά™©™±™Έ™ Ό™Θ™Ϊ™ν™�™�$�:�J�[�n�~� —�΅��� Ή�Ζ� Υ� α�λ�›››
2›=›
E›S›‰W›α› η›
�6� I�
V�0d�?•�%Υ�ϋ�$�">�#a�!…�§�ΐ�Ο� ε�ρ� �'$�QL� �� ��0�.η��&*�$Q�v�'��%°�Φ�!ι�   + ¥8 ‘ή p΅v΅‹΅+�΅7Ζ΅>ώ΅==Ά={Ά@ΉΆ>ϊΆ;9£Eu£5»£8ρ£7*¤@b¤8£¤3ά¤[¥Bl¥――¥@_¦R ¦ σ¦ �¦ §§+1§)]§‡§�§ ²§6Σ§6
¨A¨1_¨‘¨®¨ ³¨ΐ¨�¨ζ¨©©q ©l’©v�©Xv�SΟ�A#«He«7®« ζ«ς«)¬0¬4@¬u¬z¬€¬�¬�¬»¬
Α¬Ο¬Χ¬υ¬ ­­#­;:­&v­�­­­�΄­$Q®v®…®–®�®®®;³® ο―ω―°°)°F°[°s°�° �°¦°Β°Ϊ°Nϊ°I± b±o±
†±A”±Φ±θ±$χ±"²?²O²$g²%�²6²²$ι²4³2C³>v³2µ³0θ³"΄$<΄a΄r΄�΄4”΄)Ι΄σ΄!
µ/µ4µ;µMµUµ,dµ‘µ¨µΉµΘµβµ4σµC(JlF·¶ώ¶··)·?·T·!g·‰·΅·Ί·Χ·ν·ΈΈ .Έ:ΈRΈgΈ�Έ†Έ�—Έ Ή %Ή"1ΉTΉcΉ!tΉ–Ή§ΉΈΉ ΐΉΜΉΣΉάΉλΉΊΊ 2Ί?ΊWΊ^Ί²oΊ"»'»6»I»]»p»�»΅»·»Ξ»ι»ύ»Ό(Ό
8ΌFΌ UΌ _ΌiΌ{Ό�ΌΆΌΈΌ ΛΌ ΥΌ
αΌοΌ
υΌ
½½(½+7½
c½q½:‡½Β½
Κ½Ψ½
μ½χ½�½ ΎΎ'Ύ7Ύ:OΎ�Ύ›ΎOΊΎ<
ΏGΏMΏcΏDzΏ>ΏΏWώΏQVΐ_¨ΐKΑTΑnΑ‡Α—Α΄ΑOΠΑ Β5ΒDΒ;SΒ �ΒY›ΒυΒύΒ
ΓΓ0&Γ
WΓbΓ5wΓ
­ΓWΈΓΔ=�ΔΞΔγΔ%Ε)ΕGΕVΕiΕ"{Ε �Ε$ΏΕδΕ(Ζ+*Ζ)VΖ€Ζ‡Ζ �Ζ&›Ζ$ΒΖ%ηΖ#
Η1Η,BΗoΗwΗ�Η�Η
°Η»Η&ΒΗ ιΘυΘϊΘ%Ι)Ι/Ι
7ΙBΙARΙ ”Ι/µΙεΙ ΚΚΚ/)Κ3YΚ3�Κ4ΑΚWφΚNΛcWΛ»Λ ΎΛΛΛ ΤΛαΛ κΛφΛ ΜΜ Μ4ΜEΜ@MΜ�Μ: ΜΫΜλΜϋΜFΝVΝuΝO‡Ν!ΧΝωΝΞ,Ξ
EΞ$PΞ&uΞ�ΞΊΞ ΜΞνΞςΞ ϋΞ ΟΟ %Ο1Ο=BΟG€ΟΘΟΠΟ#ΰΟΠΠ*Π
3Π >ΠJΠYΠbΠ hΠ
tΠΠ�Π–Π«ΠΔΠαΠώΠΡ&Ρ"8Ρ[ΡxΡ €Ρ�Ρ_�Ρ�Ρ�#�(�7�?�E�I� `� m� y� †�’�•�#―�Σ� κ� Σ%ΣAΣ)\Σ†Σ–Σ*­ΣΨΣυΣ Τ*Τ1DΤBvΤ$ΉΤ ήΤ�Τ"Υ8Υ2PΥƒΥ�Υ-ΈΥζΥόΥ
Φ Φ
!Φ/Φ7ΦFΦYΦJkΦ<¶Φ2σΦ&Χ$.ΧSΧlΧ@sΧ΄ΧΜΧJβΧ-Ψ3Ψ
7Ψ EΨ
RΨ]ΨfΨ0|Ψ<­Ψ#κΨΩ,$Ω4QΩ*†Ω4±ΩζΩ ώΩ"
Ϊ(-ΪVΪuΪzΪ�Ϊ'ΆΪ,ΚΪ χΪΫ "Ϋ5,Ϋ bΫ
oΫ
}Ϋ �Ϋ8•Ϋ'ΞΫ'φΫ,άKά<jά-§άΥά:ςά4-έ'bέ�έ�έH�έαέπέ ήήI*ή9tή#®ή/�ή1ί"4ί2Wί4�ί1Ώί$ρίΰ ΰ)ΰ8.ΰ3gΰ ›ΰ¨ΰ&Ίΰ$αΰαα
'α?5α uα�α�α©α»α+Δα πα όα βββ%β,β
;βhFβ―β·βΎβΕβΥβπβ5γ
=γHγWγfγnγ;γ»γΓγ�γγγόγ9δUδ^δrδ΅�δ.ε@εPεbε|ε�ε
–ε
΅ε¬ε$Βε%ηε
ζζ#*ζNζ3_ζ2“ζΖζ
Ψζ ζζ&ςζη"η'η&0η$Wη|η�η¥ηΔηDΦηθF/θ vθ
€θh�θχθ�θι2 ι.Sι7‚ιLΊι κκ+κHκdκkκ&{κΆκ«κ"Ύκακ
λ λλ
2λ =λ6Iλ
€λ‹λ ’λ �λ¨λ Ελ
ΟλΪλ
ΰλλλ+ μ7μUμfμƒμ�μ‘μ™μ ³μ ΏμjΙμ4ν DνQν Vνbν0vνA§ν<ιν2&ξDYξ:�ξ
Ωξηξφξ ϋξο=ο¬\ο„ π‚�πDρ5Vρ6�ρ»Γρ&ςt¦σhτN„τ–ΣτzjυευGeφ)­φ9ΧφIχ:[χ9–χ?Πχ%ψ?6ψ$vψK›ψ?ηψ;'ωecω5ΙωG�ωEGϊ*�ϊ:Έϊ®σϊ"Άϋ#Εϋ_ιϋxIό'Βόκό)ύ4,ύxaύ5Ϊύ+ώ<ώFB�(‰�
²�½�#Ζ�!κ� !t=²ΓΙ
ιχ$%-S[`<d9΅ Ϋημ
τ  0EUo‰¤¬#µ0Ωi
ItΙΎ%�
® ΉΖβ@ώ&?f‚‹‘
 «Ύ�ζο χ 
¦ΓΩ ξψ#=Pdv�›°Γ)Χ;=={�‘ ΐΰ(φX x “ ³ » Κ &Ξ …υ {


‡
2025-04-16 14:34:46 -03:00
•

¦
 ΄
ΐ
 �
Rσ
F ed Κ Aκ  ,
 9•Ϊ€p&ρω†–™z01«Sέ1!™G'Eα'΅'*Ι*6Ϊ+N/�`2π8΅;¨§>PAjdFRΟIΐ"KϊγQΤήUΆ³[5V\p�\<ύ]]:^2�^+Λ^#χ^_"_#8_\_
|_ �_
—_¥_µ_*Κ_&υ_`#`+` 1`;`R`p`�`¨`Ύ`ά`#ϊ`a-aFa%`a†a–a ¥a²aΖaίaπa�ab>b!Qbsb „b
�b�b“Άb6c?cUc#mc%‘c·cΥcνc+dB4d,wd#¤d)Θd%ςd'e#@edeƒe•e΄eΓe Ϊe2ϋeΒ.f ρf ύf7 g3Agug*�g&Έgίg*τg&hFh"[h~h �hµ�h�`iώij#j02j<cj> j?ίjCkDckA¨k;κkI&l5pl8¦l6ίl?m<Vm=“m_ΡmF1nΈxn 1o_�o2pLpgpvp0�p,Αpξp q+ q6LqCƒq+Ηq=σq*1r\rcrwr�r'�rΗrεr�ξr‰~s‰ta’tsτtRhuX»uGv \vhv/€v°v7Ώvχvώvww3.wbwiwxw'€w¨w»wΛwζwKx3Px„x—x·¦x%^y„y�y¨y°yΓyCΚy {{!{;{M{m{…{�{{
Η{&�{ω{*|Q@|’|
¦|±|Ι|Sή|2}H}%W}!}}�}"―},�}/�}B/~-r~H ~?ι~B)Gl:΄(ο-€F€^€m€<‡€2Δ€!χ€,�F�O�V�h�z�1��Ό�
Ψ�ζ�ψ�‚/ ‚NP‚S�‚Qσ‚EƒMƒbƒ~ƒ™ƒ²ƒ(Ζƒοƒ „!'„I„`„y„•„ �„·„Υ„σ„……›.… Κ…Φ…ή…
ω…† †8†I†Y† b†o† x†…†'”†Ό†Ψ†τ†‡#‡,‡Ξ@‡��,�G�a�y�'��΄�Ο� κ� ‰!‰9‰T‰h‰z‰
‹‰ ™‰¥‰½‰Ρ‰ο‰ �)�
9�G�W�]�n�€���<µ�ς�‹= ‹
^‹ i‹v‹ �‹�‹¬‹½‹Ξ‹ξ‹�H�f�%{�[΅�Eύ�C�H�b�Oy�FΙ�c�at�‚Φ�YY�³�Μ�ι�-ό� *�VK�Ά�Ί�
Κ�;Ψ� ‘m!‘�‘—‘  ‘�‘9Ύ‘ ψ‘’K’f’lu’™β’E|“Β“!Ϋ“3ύ“/1”a”t”�”'«”#Σ”.χ”#&•4J•5•+µ•α• ι•υ•' –#1–*U–&€–§–3Ό–π–φ– ——
2—@—SG—›� ��΄�)Ζ�
π�ϋ� ™™�'™#ΐ™Dδ™)�
I�W�f�<€�:½�<ψ�95›mo›
έ›`θ›I�Q�f� n�
{�
†�‘� ¨�²�Ζ� Ϋ� θ�@ς�3�FG��� �#²�VΦ�-�G�²_�*�=�O�>j�©�2Ύ�2ρ�*$ O 8c � £ � Α Χ π ΅D΅R]΅°΅·΅&Θ΅ο΅Ά!Ά4ΆGΆ MΆ
YΆgΆoΆ�Ά�Ά ΅Ά«Ά%ΗΆνΆ' £!4£V£p£#€£&¤£Λ£Σ£γ£`χ£X¤
x¤†¤‹¤΅¤²¤Έ¤½¤Ϊ¤ρ¤¥¥0¥'5¥/]¥�¥,­¥"Ϊ¥#ύ¥&!¦.H¦w¦�¦/―¦*ί¦
2026-01-27 15:22:12 -03:00
§+*§V§:t§W―§6¨$>¨c¨){¨!¥¨<Η¨(©(-©<V©“© ­© Ί© Ζ©�©
α©ο©��Y/�F‰�?Π�«%«>«Y«I`«�«Δ«NΪ«)¬/¬6¬J¬ [¬g¬m¬<„¬HΑ¬+
­6­'O­4w­*¬­4Χ­ ®&®/9®3i®)�®Η®Μ®γ®3ό®60―g―w―•―N¤―σ―°°'°?8°,x°*¥°2Π°±?±5_±•±>°±5ο±,%²R²X²Qa²³²Ι² ι²υ²Β
³CΝ³0΄AB΄7„΄,Ό΄?ι΄C)µ<mµ5�µ ΰµκµόµ:8=v �6―¶2ζ¶·0·I·J`·
«·Ή·Χ·κ·
ώ·& Έ
0Έ>Έ MΈ WΈaΈjΈsΈ†Έe•Έ
ϋΈΉΉΉ 'ΉHΉ2dΉ—Ή Ή―ΉΑΉΚΉ?ΪΉ Ί&Ί<ΊSΊ sΊ>”Ί ΣΊΰΊ!ϋΊΈ»Φ»ι»ώ»Ό%3ΌYΌ bΌ oΌ|Ό*�Ό.ΓΌςΌψΌ!½2½?G½<‡½Δ½Ϊ½ο½$�½$Ύ,Ύ3Ύ,;Ύ(hΎ‘Ύ§ΎΕΎδΎEψΎ>ΏGTΏ �Ώ¦Ώj¶Ώ!ΐ
)ΐ&4ΐ9[ΐ6•ΐ@Μΐ]
Α kΑxΑ'‘ΑΉΑΨΑαΑ)ωΑ #Β-Β*DΒ+o›°Β'ΐΒ
θΒ
φΒ>ΓCΓ\Γ cΓpΓΓ�îþΓ
ΕΓ#ΣΓ4χΓ,ΔLΔ4kΔ Δ§Δ ―ΔΉΔΣΔγΔtμΔaΕ qΕ~Ε ƒΕ�Ε<¨ΕEεΕD+Ζ=pΖO®ΖHώΖGΗVΗeΗkΗ}ΗR™Η­μΗ‘�Θ�,ΙJ·Ι9Κ:<ΚΫwΚYSΛ�­Μi:Ν^¤Ν¬Ξ‚°Ξ�3ΟNΌΟ7 ΠACΠ>…Π<ΔΠ9ΡE;Ρ�Ρ@ Ρ-αΡX� h�B ΣsLΣ>ΐΣZ�Σ]ZΤ(ΈΤHαΤ·*Υ(βΥ) Φf5Φ…�Φ)"ΧLΧ*hΧ7“Χ|ΛΧ;HΨ2„Ψ·ΨVΠΩ('ΪPΪ gΪ,tΪ(΅ΪΚΪ αΪ{Ϋ~Ϋ“Ϋ™Ϋ·ΫΜΫ
ΫΫ(ζΫ)ά 9άFάKάPOάS ά
τάέ
έέ )έ5έDέSέmέ†έ! έ!Βέ δέ ήή*ή0CήvtήSλήΙ?ί- ΰ7ΰHΰ!]ΰ'ΰL§ΰ4τΰ))αSα \αfαvα‡α#¤αΘα Ϊαζαξαβ
βΊ"βέβωβ γ%γ.γBγWγvγ�γ§γΌγΨγμγδδ.8δ;gδ9£δέδρδψδ
ε#+εOε2lεf�ε)ζ%0ζVζ^ζmζ#qζ�•ζ%η+η 1η>ηQη mηzη%’ηRΈη% θl1θ&�θe_Ι+|υνM�…¬ίYΚ••T  α·=‡qΦ
!1BrC‹{ώΘ·¨φbδ©xΗN)π��
‡ cτ
��W�AvϋΕ7o
ΑsΟΘ2� κd�Λ5&ΡΦ8o‘�­nί„€Β±|γ�=ζp°ΠVbΫ‰ΈθeχqΚ‘v9ύ‚a%TΓµj!�9‰φnζ�(ϋ1ΠM�XPη­Δt�FTQ»�’ξϋ£η@&yfό}\χ#:ΞU/άΙ0#„I™ΙHK€�ά,,q°θ‘@w®?c΄5>¨ ³MδIΨ�-†Ϋ_O­9�^ψβ¬�!S
u�ΎhjΎ�©Fψ†~οl¤h.©�
3-Δ–k±lΰε}ΏςFη 9)Κw*�]ξcΡλ[¥y$JLι��P�\ώ¬S5�›ϊΐ6�;" )pW ,lx�Χ&C 2ψ�Ήi�΄v’/Ν%Ω�~�zD.υL�'�ΐdόrmΖoμ^„bAL~�Q“ΥΘ�΅‰ςh@ΊΠ»€NS‚—ω½§|λ6�R^u.Zγ�">†“£θτ/χ‡nωkϊΥ�w*•G#(g¤° –β�ι]�ΨΓzV–β;{$;ΞE\Ζ<†ς1—RDZ]λΕ_»•sΥΧSjενέGG(Ώ m?γ0ώΝ”›ƒtΦH)§`υ+i‡Ν�w½Y@I«a‰�²'cO4‚―:
zπ}K‹―ƒP5ο{ϊΓ<hE�ECH΅FάU�ε EƒX’ύoτu1mΰ4έ�
ΌOΔ‹“Σο”�_νζΫ…4Ρ+ΌΆ<DΒδΟΩz®�½–�P"'µyr¥Ά�*v-J>΅VΉQXZB(ΈΤ‹¦<7Vd3‘Τ 0�3[ΉK+¦¤Ax#αή³a:µΪΩΧ�ΞyΈ£N/Rf`²π'Ηm-7―®rΐuΣ$ΟΖY� ΄|!e™ω2�pWiήΤέΪί±p kΜ^;A²g……ιG’‚Y—�%Λμ¥σ8™Ηd~LgU\g΅e3„Μό}t0fΣ�Ύ Α�CHZaO³”φ8”Xfb�JIρ4�JΏRΰή.lΜ›{ρ€Ε$q%s2&?«Ό>=« ρx6 `α›ΑƒΊNσUΊ: T�“*7�κk—κQ"μ6,[¦¨W�DξsintBΪ=·`ΛMj�[Ψ?B] �Ά™8§σύKΒ
<h5>Advanced VPN Firewall Configuration</h5>
2025-04-16 11:31:08 -03:00
<p>
This interface serves as a comprehensive tool for managing firewall rules, enabling users to implement advanced traffic policies between VPN peers and networks. It simplifies establishing firewall rules, packet filtering, and NAT configurations, allowing for precise control over network security. Users can define source and destination IP addresses, ports, protocols, and actions to tailor traffic flow, ensuring a secure and efficient networking environment.
</p>
<h5>Destination Selection</h5>
<p>
You have the option to apply this rule to a specific IP address or network and/or to multiple peers as the destination.<br><br>
Enabling the "Include peer networks" option will automatically include all Allowed IPs associated with each selected peer as the destination.<br><br>
Please note that selecting multiple peers with included networks on both the source and destination ends may result in a rapid increase in the number of firewall rules generated, depending on your configuration.<br><br>
The "Not Destination" option negates the selected destination IP, network, or peer(s).
</p>
2026-03-13 20:44:45 -03:00
<h5>Protocol and Port</h5>
<p>
Only the most commonly used protocols are listed here. If you require a specific protocol, please open an issue on GitHub.<br><br>
Selecting TCP+UDP will result in the duplication of generated rules.<br><br>
Ports can be specified as single numbers (e.g., 8080) or as ranges (e.g., 8001:8999).
</p>
<h5>Source Selection</h5>
<p>
You have the option to apply this rule to a specific IP address or network and/or to multiple peers.<br><br>
Enabling the "Include peer networks" option will automatically include all Allowed IPs associated with each selected peer.<br><br>
Please note that selecting multiple peers with included networks on both the source and destination ends may result in a rapid increase in the number of firewall rules generated, depending on your configuration.<br><br>
2026-11-17 16:03:37 -03:00
The "Not Source" option negates the selected source IP, network, or peer(s).
</p>
DNS servers pushed to peers.
<br>
2026-03-18 11:24:10 -03:00
Using the internal IP as primary DNS enables internal name resolution
and DNS filtering.
Enforces routing rules defined by routing templates using firewall rules.
<br>
Peers with a default route (0.0.0.0/0) are not restricted.
<br><br>
Note: depending on the number of routes and peers, this option may generate
a large number of firewall rules.
Internal IP address and netmask used by the WireGuard interface.
2026-03-15 17:31:19 -03:00
Interval used to refresh WireGuard status information in the web UI.
Optional name used only for display in the web interface.
Public hostname or IP address and UDP port used by peers to connect.
<br>
The <b>listen port</b> must be exposed and mapped in your Docker compose (YAML) file.
WireGuard private and public keys for this interface.
<br>
The private key must remain secret.
Changing it requires updating all peer configurations.
2025-04-15 12:16:50 -03:00
<h5>Default Ports</h5>
<p>The default <code>docker-compose.yml</code> file specifies the <b>TCP</b> port range <b>8080-8089</b>. If you wish to change the port forwarding to a different range, you must manually edit the <code>docker-compose.yml</code> file and rerun the Docker Compose step outlined in the <a href="https://github.com/eduardogsilva/wireguard_webadmin?tab=readme-ov-file#deployment">deployment instructions</a>.</p>
<h5>Destination Type: Peer</h5>
<p>Port redirection will prioritize the first Peer IP address assigned a priority of Zero.</p>
<h5>Destination Type: IP Address</h5>
<p>Port forwarding rules will redirect to the specified IP address. Remember to allocate the IP address or network to a Peer.</p>
<h5>Adding a Forward Rule</h5>
<p>Automatically generates a forwarding rule to accommodate stricter firewall settings.</p>
<h5>Masquerade Source</h5>
<p>This serves as a temporary solution when a peer does not use the VPN as its default gateway. It's important to note that this configuration is not recommended, as it alters the source address of all connections to match the IP address of the WireGuard instance.</p>
<h5>Deny Policy</h5>
<p>A Deny policy blocks all access to the matched routes.</p>
<h5>Protected Policy</h5>
<p>A Protected policy requires users to authenticate before accessing the application.</p>
<ul>
<li><strong>Allowed Groups</strong>: Limits access to specific user groups. Note: Using groups requires selecting an Authentication Method of type "Local Password".</li>
<li><strong>Authentication Methods</strong>: Specify which methods users can use to authenticate (e.g., Local Password, TOTP, OIDC).</li>
</ul>
<h5>Public Policy</h5>
<p>A Public policy allows access to the application without requiring any authentication.</p>
<div class="alert alert-warning">
This hostname is used to access WireGuard WebAdmin. If the certificate cannot be issued,
2026-02-09 22:07:48 -03:00
your browser will show a security warning until the problem is fixed.
</div>
<h4>Authentication Types</h4>
<p>Select how users will authenticate through this method.</p>
2025-12-29 18:30:39 -03:00
<h5>Local Password</h5>
2026-03-12 18:54:37 -03:00
<p>Users will authenticate using a standard username and password stored locally. Only one of this type can be created.</p>
<h5>OIDC (OpenID Connect)</h5>
<p>Users will authenticate via an external identity provider (like Keycloak or Google). Requires Provider URL, Client ID, and Client Secret.</p>
<h5>TOTP (Time-Based One-Time Password)</h5>
<p>Users will need to enter a rotating token from an authenticator app. If a user does not have a personal TOTP configured, the <strong>Global TOTP Secret</strong> will be used instead. </p>
<h4>Gatekeeper User</h4>
2026-03-13 20:44:45 -03:00
<p>Gatekeeper users are used for authenticating against protected applications managed by this gateway.</p>
<h5>Password</h5>
<p>Required when creating a user. When editing, leave both password fields blank to keep the current password.
Passwords are stored using <strong>Argon2id</strong> hashing.</p>
<h5>TOTP Secret</h5>
<p>Optional per-user TOTP secret. When set, this user will authenticate using their own secret instead of the
2026-11-20 21:58:17 -03:00
global TOTP secret configured on the Authentication Method. Use the buttons below the field to generate a
random secret and scan the QR code with your authenticator app. Validate the secret by entering the current
6-digit PIN before saving.</p>
<h4>User Levels</h4>
<h5>Debugging Analyst</h5>
<p>Access to basic system information and logs for troubleshooting. No access to modify settings or view sensitive data such as peer keys.</p>
<h5>View Only</h5>
<p>Full view access, including peer keys and configuration files. Cannot modify any settings or configurations.</p>
<h5>Peer Manager</h5>
<p>Permissions to add, edit, and remove peers and IP addresses. Does not include access to modify WireGuard instance configurations or higher-level settings.</p>
2026-03-12 18:54:37 -03:00
<h5>Wireguard Manager</h5>
<p>Authority to add, edit, and remove configurations of WireGuard instances.</p>
<h5>Administrator</h5>
<p>Full access across the system. Can view and modify all settings, configurations and manage users. </p>
<br>
<h4>Peer Groups</h4>
<p>Select which peer groups this user can access. If no peer groups are selected, the user will have access to all peers.</p>
<h4>Console</h4>
<p>Enable or disable web console access for this user.</p>
2025-04-15 12:16:50 -03:00
<h4>Enhanced Filter</h4>
<p>This option filters the API status response to include only peers that the user has access to. Depending on the size of your environment, enabling this option may impact performance. To mitigate this, consider increasing the "Web Refresh Interval" to reduce the number of requests.</p>
2025-12-29 18:30:39 -03:00
<h5>API Keys</h5>
2026-01-16 15:01:13 -03:00
<p>API Keys allow external applications to interact with the WireGuard WebAdmin API.</p>
<p><strong>Token:</strong> The secret token used for authentication. Keep this secure.</p>
<p><strong>Allowed Instances:</strong> The WireGuard instances this key can manage. If none are selected, the key has access to ALL instances.</p>
<p><strong>Permissions:</strong> specific actions allowed for this key.</p>
<h5>Application Route</h5>
<p>A Route defines a path prefix within this Application that requires a specific Access Policy.</p>
<ul>
<li><strong>Route Name</strong>: An internal identifier for this route (e.g., "public_api", "admin_area"). Used for reference and exports.</li>
<li><strong>Path Prefix</strong>: The URL path that triggers this route (e.g., <code>/api/</code> or <code>/admin/</code>). Use <code>/</code> to match all remaining paths.</li>
<li><strong>Policy</strong>: The Access Policy that will be enforced when a user accesses this path.</li>
<li><strong>Order</strong>: Determines the priority of this route when evaluating the request. Lower numbers are evaluated first. If multiple routes match a path, the one with the lowest order wins.</li>
</ul>
<h5>Application</h5>
<p>Define the main details of the application you want to expose through the gateway.</p>
<ul>
<li><strong>Name</strong>: A unique internal identifier for this application (e.g., "wiki", "crm"). Contains only letters, numbers, hyphens, or underscores.</li>
<li><strong>Display Name</strong>: A friendly, human-readable name for display purposes.</li>
<li><strong>Upstream</strong>: The destination URL where requests will be forwarded (e.g., <code>http://10.188.18.27:3000</code>). Must start with <code>http://</code> or <code>https://</code>.</li>
</ul>
<h5>Cluster Enabled</h5>
<p>When disabled, workers are refused and shut down their WireGuard interfaces, and App Gateway applications are only published by this primary server. Requires the WireGuard status cache.</p>
2026-11-20 21:58:17 -03:00
<h5>Primary Enable WireGuard</h5>
<p>Lists this primary server as an option when downloading peer configurations and VPN invites.</p>
<h5>Cluster Mode</h5>
<p><strong>Mirror</strong>: every worker receives the same WireGuard instances, peers, firewall and DNS configuration. Peers can connect to any server.</p>
<p><strong>Distributed</strong>: each WireGuard instance runs only on the server selected in the instance settings (the primary server by default). Peers connect to that server. Firewall rules cannot be bound to a specific instance interface: use wg+ or IP addresses. After changing the mode, apply the WireGuard configuration so the primary server stops the instances that moved to workers.</p>
<h5>Worker Display</h5>
<p>How workers are named in server selections (peer configuration downloads and VPN invites).</p>
<h5>IP Address List</h5>
<p>Manage specific IP addresses or networks that are allowed or denied access when using the IP Address List authentication method.</p>
<h5>IP Address & Prefix</h5>
<p>Enter a single IP address (e.g., 192.168.1.50) or a network address. Use the prefix length for CIDR notation (e.g., 24 for a /24 network). Leave prefix blank for a single host (/32 for IPv4, /128 for IPv6).</p>
<h5>Action</h5>
<p><strong>Allow</strong>: Grants access to the specified IP/network.<br>
<strong>Deny</strong>: Specifically blocks access from the specified IP/network.</p>
<h5>Description</h5>
<p>An optional note to help identify this entry (e.g., "Office Network", "Blocked Attacker").</p>
<h5>Peers</h5>
<p>Select which peers can be managed by users with this peer group.</p>
2025-04-16 10:18:23 -03:00
<h5>WireGuard Instances</h5>
2026-11-20 21:58:17 -03:00
<p>All peers in this WireGuard instance can be managed by users with this peer group, including adding or removing peers.</p>
2025-04-16 10:18:23 -03:00
<h5>Routing Templates</h5>
<p>Define routing configurations that can be applied to peers.</p>
<h5>Default Template</h5>
2026-11-20 21:58:17 -03:00
<p>If checked, this template will be the default for the selected WireGuard instance. Only one default template is allowed per instance.</p>
<h5>Route Type</h5>
<p>Select the type of routes to push to the client.</p>
<ul>
<li><strong>Default Route (0.0.0.0/0)</strong>: Redirects all traffic through the VPN.</li>
<li><strong>Routes from Peers on same Interface</strong>: Pushes routes for other peers on the same WireGuard interface.</li>
<li><strong>Routes from All Peers</strong>: Pushes routes for all peers across all interfaces.</li>
<li><strong>Custom Routes</strong>: Allows you to specify custom CIDR ranges.</li>
</ul>
2025-04-15 12:16:50 -03:00
2025-04-16 14:34:46 -03:00
<h5>Custom Routes</h5>
<p>Enter custom routes in CIDR notation, one per line (e.g., 192.168.1.0/24).</p>
<h5>Allow Peer Custom Routes</h5>
<p>If checked, allows specific peers to add their own custom routes on top of this template.</p>
<h5>Enforce Route Policy</h5>
<p>If enabled, firewall rules will be applied to strictly enforce this routing policy.<br>The peer will only be able to access networks explicitly defined by the assigned routing template.<br>Any traffic to destinations outside these routes will be blocked.</p>
<p>Note: depending on the number of routes and peers, enabling this option may generate a large number of firewall rules.</p>
<h5>Worker</h5>
<p>A worker is a cluster node that replicates WireGuard, firewall and DNS from this primary server and, optionally, publishes App Gateway applications.</p>
<h5>Name and location</h5>
<p>Used to identify the worker. The <strong>hostname</strong> is the address clients use to connect to this worker: it is written as the endpoint of the peer configurations downloaded for this server.</p>
<h5>Token</h5>
<p>Secret used by the worker to authenticate with this primary server. Changing it disconnects the worker until its configuration is updated.</p>
<h5>IP lock</h5>
<p>When enabled, the worker is only accepted from the IP address below. Without it, the address is updated automatically from the last connection.</p>
<h5>Enabled</h5>
<p>Disabled workers are refused and shut down their WireGuard interfaces until enabled again.</p>
<h5>Certificate</h5>
<p>Defines how the TLS certificate for this hostname is issued.</p>
<ul>
2026-01-27 15:22:12 -03:00
<li><strong>Trusted certificate (HTTP validation)</strong>: Issued through ACME (e.g. Let's Encrypt) and validated over HTTP. The hostname must point to this server and ports 80/443 must be reachable from the internet.</li>
<li><strong>Trusted certificate (DNS validation)</strong>: Issued through ACME and validated with a DNS record created using the selected DNS credential. The server does not need to be reachable from the internet.</li>
<li><strong>Self-signed certificate</strong>: Issued by the internal Caddy CA. Browsers will show a security warning.</li>
</ul>
<p>When the fallback option is enabled and a trusted certificate cannot be issued, a self-signed certificate is used until the next successful attempt. Without the fallback, the connection fails until the certificate is issued.</p>
<p>Use <strong>Retry certificate</strong> in the host list to request a new attempt right away, for example after fixing the DNS or firewall.</p>
<p><strong>Important:</strong> the certificate is requested as soon as the configuration is applied. With HTTP validation, the hostname must already point to this server: failed attempts count towards the Let's Encrypt limit (5 per hour per hostname). If the DNS is not ready yet, use DNS validation.</p>
'%(line)s' is not a network address. Use the network address (e.g., '%(net)s').(Share this password via a separate secure channel)<h2>Welcome to Your VPN Setup</h2>
<p>Begin by downloading the WireGuard app for your device using one of the links below.</p>
<p>Once installed, you can either <strong>scan the QR code</strong> or <strong>download the configuration file</strong> to quickly import your settings and start using your secure VPN connection.</p>A DNS credential can only be used with the DNS validation.A new certificate will be requested for %(hostname)s. The current configuration was exported.A peer can have only one IP with priority zero.A peer group with that name already exists.A worker with that name already exists.ACCEPTAPI DocumentationAPI Key deleted successfully.API Key saved successfully.API KeysAPI TokenAccess DeniedAccess PasswordAccess PoliciesAccess Policy deleted successfully.Access Policy saved successfully.ActionActionsActiveAddAdd API KeyAdd Access PolicyAdd Allowed DomainAdd Allowed EmailAdd ApplicationAdd Application HostAdd Application RouteAdd Auth MethodAdd Client routeAdd DNS CredentialAdd Filter ListAdd Forward Rule (allow)Add GroupAdd HostAdd IP AddressAdd IntervalAdd Peer GroupAdd ProfileAdd RouteAdd Routing TemplateAdd Time IntervalAdd UserAdd WireGuard InstanceAdd WorkerAddressAdministratorAllAll DNS queries will be forwarded to the primary resolver. If the primary resolver is not available, the secondary resolver will be used.AllowAllow ExportAllow ForwardAllow Instance to InstanceAllow Peer Custom RoutesAllow Peer to PeerAllow ReloadAllow RestartAllow access to everyone without authentication.Allow invalid or self-signed TLS certificates from the upstreamAllow invalid/self-signed certificateAllow traffic from VPN to WANAllowed Domain deleted successfully.Allowed Domain saved successfully.Allowed Email deleted successfully.Allowed Email saved successfully.Allowed Emails & DomainsAllowed GroupsAllowed IP or NetworkAllowed IPsAllowed InstancesAllowedIPs at Peer section of wgAllowedIPs at client configuration fileAllowing peer custom routes is not applicable when Route Type is 'Default Route'.App GatewayApplicationApplication Default Policy deleted successfully.Application Default Policy saved successfully.Application DetailsApplication Host deleted successfully.Application Host saved successfully.Application HostsApplication Route deleted successfully.Application Route saved successfully.Application RoutesApplication deleted successfully.Application saved successfully.ApplicationsApplications published by workers must use DNS validation or self-signed certificates: certificates are issued by this primary server and distributed to the workers.Applications served by cluster workers require DNS validation or self-signed certificates. Change the certificate of these hosts first: %(hosts)sApplyApply Route TemplateApply templateAre you sure you want to create a new peer?Are you sure you want to delete the API Key "%(name)s"?Are you sure you want to delete the DNS credential "%(name)s"?Are you sure you want to delete the IP address "%(address)s"?Are you sure you want to delete the access policy "%(name)s"?Are you sure you want to delete the allowed domain "%(domain)s"?Are you sure you want to delete the allowed email "%(email)s"?Are you sure you want to delete the application "%(name)s"?Are you sure you want to delete the authentication method "%(name)s"?Are you sure you want to delete the group "%(name)s"?Are you sure you want to delete the host "%(hostname)s"?Are you sure you want to delete the profile "%(name)s"?Are you sure you want to delete the route "%(name)s" (%(path)s)?Are you sure you want to delete the user "%(username)s"?Are you sure you want to delete this time interval?Are you sure you want to regenerate the token? The old token will stop working immediately.Are you sure you want to remove the default policy for "%(name)s"?At least one address does not appear in the wg show command output, which may indicate that another peer is using an overlapping IP or that the configuration file is outdated.At least one route must be provided when Route Type is 'Custom'.At least one user group must be selected when using Local Password
You're invited to join our secure WireGuard VPN network. Please click the link below to access your personalized VPN configuration:
{invite_url}
Note: This invitation link will expire in {expire_minutes} minutes. If you need a new link after expiration, please request another invite.Hide extrasHostHostnameHostname contains invalid characters.HostsHour(s)IP AddressIP Address ListIP Address cannot be used without selecting a WireGuard instance.IP Address deleted successfully.IP Address is required when IP Lock is enabled.IP Address saved successfully.IP AddressesIP LockIP Lock EnabledIP address added|IP address added successfully.IP address deleted|IP address deleted successfully.IP address updated|IP address updated successfully.IP addresses can only use a self-signed certificate.IP lock is enabled, but the worker is attempting to access from a different IP address.IdentityIf you find any issues with the translation or would like to request a new language, please open anInIn InterfaceInactiveInstallationInstanceInstance IDInstance TrafficInterfaceInterface KeysInternal IP AddressInternal NetworkInvalidInvalid Destination. Either Peer or IP Address must be informed.Invalid TOTP PIN.Invalid TOTP secret format. Must be a valid Base32 string.Invalid action.Invalid commandInvalid config fileInvalid confirmation|Please confirm deletion of WireGuard instance: wgInvalid hostname or IP AddressInvalid hostname.Invalid route format: '%(line)s'. Please use CIDR notation (e.g., 10.0.0.0/24).Invalid search domain: %(domain)sInvalid targetInvite SettingsInvite Settings|Settings saved successfully.Invite URLInvite URL must end with '/invite/'.Invite URL must start with 'https://'.Invite data is not available.Invite refreshed.Invite text copied to clipboard.KeysLanguageLast SeenLast UpdateLast reported stateLast updateLatest HandshakeLeave blank to keep the current value (ending in %(suffix)s).Leave this empty when the application is served on all cluster workers.LettersLetters, DigitsLetters, Digits, Special CharactersLinked Peers (Debug)List Peer GroupsList URLList UsersListen PortLocal PasswordLocationLoginLogin againMASQUERADEMain ip addressManageManage Firewall RuleManage Firewall SettingsManage IP address or NetworkManage Peer Schedule ProfileManage Port ForwardManage client routeMasquerade SourceMasquerade traffic from VPN to WANMaster Cache Processing TimeMembersMemory usageMessage templatesMinimum 8 characters, with at least one uppercase letter, one lowercase letter, and one number.Missing a method or feature?MondayNameNeed attentionNetmaskNeverNewNew WireGuard InstanceNext DisableNext EnableNext disableNext enableNoNo Access Policies found.No Allowed Emails or Domains found.No Applications found.No Authentication Methods found.No DNS Credentials found.No Gatekeeper Groups found.No Gatekeeper Users found.No Hosts configured for this application.No Hosts found.No IP Addresses found.No Routes configured for this application.No WireGuard Instances FoundNo WireGuard instancesNo WireGuard instances found.No active VPN invitationsNo certificate is being served for this hostname.No interfaces found|No WireGuard interfaces were found to process.No invite data available to refresh.No peers linked to this profile.No profile associatedNo recent report from this server.No report received yet.No routing templates available for this interface.No schedule profiles found.No time intervals found.No traffic history, please wait a few minutesNo workers configuredNot DestinationNot SourceNot StateNot installedNot setOIDC Client IDOIDC Client SecretOIDC Provider URLOIDC authentication is temporarily unavailable and will be available soon.OIDC fields must be empty for Local Password authentication.OIDC fields must be empty for TOTP authentication.OfflineOne route per line in CIDR notation.One-Time Password (TOTP)OnlineOnly one Local Password authentication method can be configured.Open an issue on GitHubOpenID Connect (OIDC)Optional. One or more domains separated by commas (e.g. vpn, example.com).OrderOutOut InterfacePacket StateParameters
Report-Msgid-Bugs-To:
PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE
Last-Translator: FULL NAME <EMAIL@ADDRESS>
Language-Team: LANGUAGE <LL@li.org>
Language:
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=2; plural=(n > 1);
<h5>ConfiguraΓ§Γ£o AvanΓ§ada do Firewall da VPN</h5>
2025-04-16 11:31:08 -03:00
<p>
Esta interface serve como uma ferramenta abrangente para gerenciar regras de firewall, permitindo que os usuΓ΅rios implementem polΓ­ticas de trΓ΅fego avanΓ§adas entre peers de VPN e redes. Ela simplifica o estabelecimento de regras de firewall, o filtro de pacotes e as configuraΓ§Γµes de NAT, possibilitando um controle preciso sobre a seguranΓ§a da rede. Os usuΓ΅rios podem definir endereΓ§os IP de origem e destino, portas, protocolos e aΓ§Γµes para ajustar o fluxo de trΓ΅fego, garantindo um ambiente de rede seguro e eficiente.
</p>
<h5>SeleΓ§Γ£o de Destino</h5>
<p>
Voc� tem a opção de aplicar esta regra a um endereço IP ou rede específica e/ou a múltiplos peers como destino.<br><br>
Habilitar a opΓ§Γ£o "Include peer networks" irΓ΅ incluir automaticamente todos os IPs permitidos associados a cada peer selecionado como destino.<br><br>
Por favor, note que selecionar mΓΊltiplos peers com redes incluΓ­das tanto na origem quanto no destino pode resultar em um rΓ΅pido aumento no nΓΊmero de regras de firewall geradas, dependendo da sua configuraΓ§Γ£o.<br><br>
A opΓ§Γ£o "Not Destination" nega o endereΓ§o IP, rede ou peer(s) selecionado(s).
</p>
2026-03-13 20:44:45 -03:00
<h5>Protocolo e Porta</h5>
<p>
Apenas os protocolos mais comumente utilizados estão listados aqui. Se voc� precisar de um protocolo específico, por favor, abra uma issue no GitHub.<br><br>
Selecionar TCP+UDP resultarΓ΅ na duplicaΓ§Γ£o das regras geradas.<br><br>
As portas podem ser especificadas como nΓΊmeros individuais (por exemplo, 8080) ou como intervalos (por exemplo, 8001:8999).
</p>
<h5>SeleΓ§Γ£o de Origem</h5>
<p>
Voc� tem a opção de aplicar esta regra a um endereço IP ou rede específica e/ou a múltiplos peers.<br><br>
Habilitar a opΓ§Γ£o "Include peer networks" irΓ΅ incluir automaticamente todos os IPs permitidos associados a cada peer selecionado.<br><br>
Por favor, note que selecionar mΓΊltiplos peers com redes incluΓ­das tanto na origem quanto no destino pode resultar em um rΓ΅pido aumento no nΓΊmero de regras de firewall geradas, dependendo da sua configuraΓ§Γ£o.<br><br>
2026-11-17 16:03:37 -03:00
A opΓ§Γ£o "Not Source" nega o endereΓ§o IP, rede ou peer(s) selecionado(s).
</p>
Servidores DNS enviados aos peers.
<br>
2026-03-18 11:24:10 -03:00
Usar o IP interno como DNS primΓ΅rio habilita a resoluΓ§Γ£o de nomes interna
e filtragem de DNS.
ForΓ§a as regras de roteamento definidas pelos modelos de roteamento usando regras de firewall.
<br>
Peers com uma rota padrΓ£o (0.0.0.0/0) nΓ£o sΓ£o restringidos.
<br><br>
Nota: dependendo do nΓΊmero de rotas e peers, esta opΓ§Γ£o pode gerar
um grande nΓΊmero de regras de firewall.
EndereΓ§o IP interno e mΓ΅scara de rede usados pela interface WireGuard.
2026-03-15 17:31:19 -03:00
Intervalo usado para atualizar as informaΓ§Γµes de status do WireGuard na interface web.
Nome opcional usado apenas para exibiΓ§Γ£o na interface web.
Nome de host pΓΊblico ou endereΓ§o IP e porta UDP usados pelos peers para se conectar.
<br>
A <b>listen port</b> deve estar exposta e mapeada em seu arquivo Docker compose (YAML).
Chaves privada e pΓΊblica do WireGuard para esta interface.
<br>
A chave privada deve permanecer em segredo.
AlterΓ΅-la requer a atualizaΓ§Γ£o de todas as configuraΓ§Γµes dos peers.
2025-04-15 12:16:50 -03:00
<h5>Portas PadrΓ£o</h5>
<p>O arquivo padrão <code>docker-compose.yml</code> especifica o intervalo de portas <b>TCP</b> <b>8080-8089</b>. Se voc� deseja alterar o redirecionamento de portas para um intervalo diferente, é necessário editar manualmente o arquivo <code>docker-compose.yml</code> e executar novamente a etapa do Docker Compose descrita nas <a href="https://github.com/eduardogsilva/wireguard_webadmin?tab=readme-ov-file#deployment">instruções de implantação</a>.</p>
<h5>Tipo de Destino: Peer</h5>
<p>O redirecionamento de porta darΓ΅ prioridade ao primeiro endereΓ§o IP do Peer com prioridade Zero.</p>
<h5>Tipo de Destino: EndereΓ§o IP</h5>
<p>As regras de encaminhamento de porta redirecionarΓ£o para o endereΓ§o IP especificado. Lembre-se de alocar o endereΓ§o IP ou rede para um Peer.</p>
<h5>Adicionando uma Regra de Encaminhamento</h5>
<p>Gera automaticamente uma regra de encaminhamento para acomodar configuraΓ§Γµes de firewall mais restritivas.</p>
<h5>Mascarar Fonte</h5>
<p>Isto serve como uma soluΓ§Γ£o temporΓ΅ria quando um peer nΓ£o utiliza a VPN como gateway padrΓ£o. Γ‰ importante notar que esta configuraΓ§Γ£o nΓ£o Γ© recomendada, pois altera o endereΓ§o de origem de todas as conexΓµes para corresponder ao endereΓ§o IP da instΓΆncia do WireGuard.</p>
<h5>PolΓ­tica de NegaΓ§Γ£o</h5>
<p>Uma polΓ­tica de NegaΓ§Γ£o bloqueia todo o acesso Γ s rotas correspondentes.</p>
<h5>PolΓ­tica Protegida</h5>
<p>Uma polΓ­tica Protegida exige que os usuΓ΅rios se autentiquem antes de acessar o aplicativo.</p>
<ul>
<li><strong>Grupos Permitidos</strong>: Limita o acesso a grupos de usuΓ΅rios especΓ­ficos. Nota: O uso de grupos requer a seleΓ§Γ£o de um MΓ©todo de AutenticaΓ§Γ£o do tipo "Senha Local".</li>
<li><strong>MΓ©todos de AutenticaΓ§Γ£o</strong>: Especifique quais mΓ©todos os usuΓ΅rios podem usar para se autenticar (ex: Senha Local, TOTP, OIDC).</li>
</ul>
<h5>PolΓ­tica PΓΊblica</h5>
<p>Uma polΓ­tica PΓΊblica permite o acesso ao aplicativo sem exigir nenhuma autenticaΓ§Γ£o.</p>
<div class="alert alert-warning">
Este hostname Γ© usado para acessar o WireGuard WebAdmin. Se o certificado nΓ£o puder ser emitido,
2026-02-09 22:07:48 -03:00
seu navegador exibirΓ΅ um alerta de seguranΓ§a atΓ© que o problema seja corrigido.
</div>
<h4>Tipos de AutenticaΓ§Γ£o</h4>
<p>Selecione como os usuΓ΅rios irΓ£o se autenticar atravΓ©s deste mΓ©todo.</p>
2025-12-29 18:30:39 -03:00
<h5>Senha Local</h5>
2026-03-12 18:54:37 -03:00
<p>Os usuΓ΅rios se autenticarΓ£o usando um nome de usuΓ΅rio e senha padrΓ£o armazenados localmente. Apenas um deste tipo pode ser criado.</p>
<h5>OIDC (OpenID Connect)</h5>
<p>Os usuΓ΅rios se autenticarΓ£o por meio de um provedor de identidade externo (como Keycloak ou Google). Requer URL do Provedor, ID do Cliente e Segredo do Cliente.</p>
<h5>TOTP (Senha de Uso Γ�nico Baseada em Tempo)</h5>
<p>Os usuΓ΅rios precisarΓ£o inserir um token rotativo de um aplicativo autenticador. Se um usuΓ΅rio nΓ£o tiver um TOTP pessoal configurado, o <strong>Segredo TOTP Global</strong> serΓ΅ usado em seu lugar.</p>
<h4>UsuΓ΅rio do Gatekeeper</h4>
2026-03-13 20:44:45 -03:00
<p>UsuΓ΅rios do Gatekeeper sΓ£o usados para autenticaΓ§Γ£o em aplicaΓ§Γµes protegidas gerenciadas por este gateway.</p>
<h5>Senha</h5>
<p>ObrigatΓ³rio ao criar um usuΓ΅rio. Ao editar, deixe ambos os campos de senha em branco para manter a senha atual.
As senhas sΓ£o armazenadas usando hash <strong>Argon2id</strong>.</p>
<h5>Segredo TOTP</h5>
<p>Segredo TOTP opcional por usuΓ΅rio. Quando definido, este usuΓ΅rio irΓ΅ se autenticar usando seu prΓ³prio segredo em vez do
2026-11-20 21:58:17 -03:00
segredo TOTP global configurado no MΓ©todo de AutenticaΓ§Γ£o. Use os botΓµes abaixo do campo para gerar um
segredo aleatΓ³rio e ler o cΓ³digo QR com seu aplicativo autenticador. Valide o segredo inserindo o PIN atual de
6 dΓ­gitos antes de salvar.</p>
<h4>NΓ­veis de UsuΓ΅rio</h4>
<h5>Analista de Debug</h5>
<p>Acesso a informaΓ§Γµes bΓ΅sicas do sistema e logs para soluΓ§Γ£o de problemas. Sem acesso para modificar configuraΓ§Γµes ou visualizar dados sensΓ­veis, como chaves de peer.</p>
<h5>Somente VisualizaΓ§Γ£o</h5>
<p>Acesso total de visualizaΓ§Γ£o, incluindo chaves de peer e arquivos de configuraΓ§Γ£o. NΓ£o pode modificar nenhuma configuraΓ§Γ£o ou ajuste.</p>
<h5>Gerente de Peers</h5>
<p>PermissΓµes para adicionar, editar e remover peers e endereΓ§os IP. NΓ£o inclui acesso para modificar configuraΓ§Γµes de instΓΆncias do WireGuard ou configuraΓ§Γµes de nΓ­vel superior.</p>
2026-03-12 18:54:37 -03:00
<h5>Gerente do WireGuard</h5>
<p>Autoridade para adicionar, editar e remover configuraΓ§Γµes de instΓΆncias do WireGuard.</p>
<h5>Administrador</h5>
<p>Acesso total ao sistema. Pode visualizar e modificar todas as configuraΓ§Γµes, ajustes e gerenciar usuΓ΅rios.</p>
<br>
<h4>Grupos de Peers</h4>
<p>Selecione quais grupos de peers este usuΓ΅rio pode acessar. Se nenhum grupo de peers for selecionado, o usuΓ΅rio terΓ΅ acesso a todos os peers.</p>
<h4>Console</h4>
<p>Ativar ou desativar o acesso ao console web para este usuΓ΅rio.</p>
2025-04-15 12:16:50 -03:00
<h4>Filtro Aprimorado</h4>
<p>Esta opΓ§Γ£o filtra a resposta do status da API para incluir apenas os peers aos quais o usuΓ΅rio tem acesso. Dependendo do tamanho do seu ambiente, ativar esta opΓ§Γ£o pode impactar o desempenho. Para mitigar isso, considere aumentar o "Intervalo de AtualizaΓ§Γ£o da Web" para reduzir o nΓΊmero de requisiΓ§Γµes.</p>
2025-12-29 18:30:39 -03:00
<h5>Chaves de API</h5>
2026-01-16 15:01:13 -03:00
<p>As Chaves de API permitem que aplicativos externos interajam com a API do WireGuard WebAdmin.</p>
<p><strong>Token:</strong> O token secreto usado para autenticaΓ§Γ£o. Mantenha-o seguro.</p>
<p><strong>InstΓΆncias Permitidas:</strong> As instΓΆncias do WireGuard que esta chave pode gerenciar. Se nenhuma for selecionada, a chave terΓ΅ acesso a TODAS as instΓΆncias.</p>
<p><strong>PermissΓµes:</strong> aΓ§Γµes especΓ­ficas permitidas para esta chave.</p>
<h5>Rota de AplicaΓ§Γ£o</h5>
<p>Uma Rota define um prefixo de caminho dentro desta AplicaΓ§Γ£o que requer uma PolΓ­tica de Acesso especΓ­fica.</p>
<ul>
<li><strong>Nome da Rota</strong>: Um identificador interno para esta rota (ex: "public_api", "admin_area"). Usado para refer�ncia e exportações.</li>
<li><strong>Prefixo do Caminho</strong>: O caminho da URL que aciona esta rota (ex: <code>/api/</code> ou <code>/admin/</code>). Use <code>/</code> para corresponder a todos os caminhos restantes.</li>
<li><strong>PolΓ­tica</strong>: A PolΓ­tica de Acesso que serΓ΅ aplicada quando um usuΓ΅rio acessar este caminho.</li>
<li><strong>Ordem</strong>: Determina a prioridade desta rota ao avaliar a solicitaΓ§Γ£o. NΓΊmeros menores sΓ£o avaliados primeiro. Se vΓ΅rias rotas corresponderem a um caminho, a de menor ordem vence.</li>
</ul>
<h5>AplicaΓ§Γ£o</h5>
<p>Defina os detalhes principais da aplicação que voc� deseja expor através do gateway.</p>
<ul>
<li><strong>Nome</strong>: Um identificador interno ΓΊnico para esta aplicaΓ§Γ£o (ex: "wiki", "crm"). ContΓ©m apenas letras, nΓΊmeros, hΓ­fens ou sublinhados.</li>
<li><strong>Nome de ExibiΓ§Γ£o</strong>: Um nome amigΓ΅vel e legΓ­vel para fins de exibiΓ§Γ£o.</li>
<li><strong>Upstream</strong>: A URL de destino para onde as solicitaΓ§Γµes serΓ£o encaminhadas (ex: <code>http://10.188.18.27:3000</code>). Deve comeΓ§ar com <code>http://</code> ou <code>https://</code>.</li>
</ul>
<h5>Cluster Habilitado</h5>
<p>Quando desabilitado, os workers sΓ£o recusados e desligam suas interfaces WireGuard, e as aplicaΓ§Γµes do App Gateway sΓ£o publicadas apenas por este servidor primΓ΅rio. Requer o cache de status do WireGuard.</p>
2026-11-20 21:58:17 -03:00
<h5>Habilitar WireGuard Principal</h5>
<p>Lista este servidor primΓ΅rio como opΓ§Γ£o ao baixar configuraΓ§Γµes de peer e convites de VPN.</p>
<h5>Modo do Cluster</h5>
<p><strong>Mirror</strong>: todos os workers recebem as mesmas instΓΆncias do WireGuard, peers, firewall e configuraΓ§Γ£o de DNS. Os peers podem se conectar a qualquer servidor.</p>
<p><strong>Distributed</strong>: cada instΓΆncia do WireGuard roda apenas no servidor selecionado nas configuraΓ§Γµes da instΓΆncia (por padrΓ£o, o servidor primΓ΅rio). Os peers se conectam a esse servidor. Regras de firewall nΓ£o podem ser vinculadas Γ  interface de uma instΓΆncia especΓ­fica: use wg+ ou endereΓ§os IP. Depois de trocar o modo, aplique a configuraΓ§Γ£o do WireGuard para que o servidor primΓ΅rio pare as instΓΆncias que foram para os workers.</p>
<h5>ExibiΓ§Γ£o do Worker</h5>
<p>Como os workers sΓ£o identificados nas seleΓ§Γµes de servidor (download de configuraΓ§Γµes de peer e convites de VPN).</p>
<h5>Lista de EndereΓ§os IP</h5>
<p>Gerencie endereços IP ou redes específicas que t�m acesso permitido ou negado ao usar o método de autenticação por Lista de Endereços IP.</p>
<h5>EndereΓ§o IP e Prefixo</h5>
<p>Insira um ΓΊnico endereΓ§o IP (ex: 192.168.1.50) ou um endereΓ§o de rede. Use o comprimento do prefixo para notaΓ§Γ£o CIDR (ex: 24 para uma rede /24). Deixe o prefixo em branco para um ΓΊnico host (/32 para IPv4, /128 para IPv6).</p>
<h5>AΓ§Γ£o</h5>
<p><strong>Permitir</strong>: Concede acesso Γ  rede/IP especificado.<br>
<strong>Negar</strong>: Bloqueia especificamente o acesso da rede/IP especificado.</p>
<h5>DescriΓ§Γ£o</h5>
<p>Uma nota opcional para ajudar a identificar esta entrada (ex: "Rede do EscritΓ³rio", "Atacante Bloqueado").</p>
<h5>Peers</h5>
<p>Selecione quais peers podem ser gerenciados por usuΓ΅rios com este grupo de peers.</p>
2025-04-16 10:18:23 -03:00
<h5>InstΓΆncias do WireGuard</h5>
2026-11-20 21:58:17 -03:00
<p>Todos os peers nesta instΓΆncia do WireGuard podem ser gerenciados por usuΓ΅rios com este grupo de peers, incluindo a adiΓ§Γ£o ou remoΓ§Γ£o de peers.</p>
2025-04-16 10:18:23 -03:00
<h5>Modelos de Roteamento</h5>
<p>Defina configuraΓ§Γµes de roteamento que podem ser aplicadas aos peers.</p>
<h5>Modelo PadrΓ£o</h5>
2026-11-20 21:58:17 -03:00
<p>Se marcado, este modelo serΓ΅ o padrΓ£o para a instΓΆncia WireGuard selecionada. Apenas um modelo padrΓ£o Γ© permitido por instΓΆncia.</p>