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

568 lines
121 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 “ ³ » Κ &Ξ …υ {


‡
•

¦
 ΄
ΐ
 �
Rσ
F ed Κ Dκ /
j7CΆJζ11c‹g�σ„�@LT ΅ �­%dJ&§―(W)Sj*ƒΎ-�B1"Π6�σ8��<59?†oD5φG*,IWPοpTQ`Z8²Z%λZ<\\N\3«\+ί\# ]/]7]"P]!s]
•] £]°]ΐ]Φ],λ]+^D^L^U^\^d^y^•^%―^Υ^ι^_!$_F_[_r_$�_
―_ ½_
Κ_Υ_η_ώ_
`!`<`X`h`„`
“`
�`¬`y²`,a5aKa"]a%€a¦aΔaΥa.ηaAb+Xb„b*£b)Ξb6ψb5/c+ec‘c£ccΕc!Ϋc6ύcf4d ›d §dC³dBχd:e,Ue+‚e®e/Ζe.φe%f$=f#bf †f±“fΆEgθg!πgh)$h@NhB�hD�hGiG_iR§i?ϊiM:j9�j<Βj:�jC:k?~k>ΎkeύkQclµlQ5ma‡mιmnn-n2Gn1zn¬nΗn,ήn, o(8o*ao<�o,Ιoφoύopp'2pZptp�}p
q��qX&rvrRφrSIsB�s ΰsμs/t4t5Ctyt€t�t�t"·tΪtαtσt/ϋt+u>uNuiuS…u4Ωuv"vµ1v$ηv w#w9wAwTw>[w �x§x­xΗxΩxωxy(yDy
Ty!_y�y�y\Ώyz 5zAz\z]qzΟzβz'ρz&{@{"Q{+t{/ {CΠ{,|<A|:~|HΉ|D}9G}*�}-¬}Ϊ}π}~A~1^~#�~)΄~ ή~θ~π~!7:$r—²Λλ?€KD€Q�€Lβ€/�8�N�k�&†�­�3Β�φ�‚"3‚V‚n‚�‚§‚
Ύ‚ Μ‚ν‚
ƒ'ƒ/ƒ Gƒ θƒυƒύƒ
„'„!7„Y„k„{„ „„‘„
�„¨„(½„ζ„ύ„…(…D…L…µ`…††3†N†$g†�†1�†Ρ†μ†
‡+‡A‡\‡y‡�‡�‡
°‡Ύ‡Ν‡ε‡"ϋ‡�=�X�
g�u�…�‹���―�Γ�?ά�‰.‰:@‰
{‰†‰�‰¬‰ ΄‰ ΐ‰ Μ‰ Φ‰χ‰�F"�i�#�f£�I
‹T‹Z‹w‹6“‹FΚ‹U�Ng�Y�P�a� ��Ά�-΄�β�_�b�y���<›� Ψ�mδ�R�Z� c�m�3�� µ�Ώ�EΧ��U,�z‚�Cύ�A‘!X‘3z‘-®‘ά‘ο‘ ’)&’(P’1y’%«’@Ρ’@“7S“‹“““›“,°“+έ“. ”-8”f”5}”³”»”Ν”β”φ”••–&–+–2:–m–s–
{–‰–J΅–&μ–I—%]—ƒ—
’— —&Ή—(ΰ—, �?6�mv� δ�dξ�S™[™o™ x™ …™ �™™™²™»™Ξ™ δ™ π™5ϊ™0�GE��� �#²�HΦ�›=›ZW›+²›ή›π›D�S�$f�#‹�$―�Τ�-ν��"�)�?�V�o�†�H��Oα�1�8�'I�q���΅�±�Α�Θ�
2026-01-27 15:22:12 -03:00
Ϊ�ε�υ�� � $�.�$J�o�*‚� ­�Ξ�ε�χ�* A J Y ^o %Ξ τ ϊ ΅΅%΅+΅1΅K΅c΅x΅�΅¥΅*¨΅AΣ΅"Ά08Ά&iΆ*�Ά,»Ά0θΆ£$5£0Z£&‹£²£*Ρ£ό£=¤GZ¤,Ά¤&Ο¤φ¤+
¥(9¥Ab¥,¤¥'Ρ¥.ω¥(¦
D¦ O¦ Y¦ c¦p¦¦’¦�¦UΑ¦Q§@i§
�§&Έ§!ί§ ¨M ¨Y¨u¨M‹¨Ω¨ί¨ζ¨ω¨ © ©$©>A©D€©-Ε©σ©0�;C�1�;±�ν� «1«6N«*…«°«µ«Μ«*ε«4¬E¬U¬j¬Sy¬Ν¬έ¬ν¬ό¬?­&N­,u­0Ά­Σ­Bο­82®k®B‡®0Κ®0ϋ®,― 2―D<―�―�―·―ΐ―QΦ―I(°r°'�°0΄°%ε°@ ±FL±3“±6Η± ώ±²²=!²=_²�² ΄²-Υ²,³0³G³[³Ip³ Ί³Η³δ³φ³ ΄΄
/΄=΄ O΄ Y΄ c΄m΄v΄�΄k™΄
µµµ!µ$7µ!\µ:~µ ΉµΓµΣµ κµτµ? DPcv!’¶C΄¶ ψ¶·.·“M·α·�·Έ'ΈDΈ[ΈcΈ uΈ‚Έ0�Έ4ΞΈΉ Ή#"ΉFΉI`Ή?�ΉκΉΊΊ*/ΊZΊbΊ jΊ-tΊ,ΆΊΟΊιΊ" »,»MC»‘»O�» ϊ»ΌwΌ�Ό –Ό'ΆΌ;ΚΌ=½?D½[„½ ΰ½μ½)Ύ .ΎOΎXΎ)oΎ ™Ύ£Ύ.½Ύ5μΎ"Ώ7Ώ$FΏ
kΏyΏ9�ΏΒΏΘΏ ΟΏΩΏ θΏ ΐΐ'ΐ
.ΐ%<ΐ2bΐ$•ΐΊΐ7Τΐ ΑΑ Α%Α@Α
PΑr[ΑΞΑ ήΑλΑ πΑύΑ;ΒFQΒO�Β>θΒZ'ΓI‚ΓΜΓγΓψΓώΓΔR-Δ°€Δ^1Εe�Ε6φΕ7-Ζ8eΖ·�ΖVΗ†tΘqϋΘcmΙ¦ΡΙxΚ–ψΚN�Λ0ήΛEΜHUΜ:�Μ5ΩΜGΝWΝAvΝ.ΈΝZηΝMBΞ1�ΞdΒΞ>'Ο\fΟVΓΟΠB7Π�zΠ%Ρ&=ΡcdΡ|ΘΡ+E�q�)��;�qς�;dΣ4 Σ³ΥΣY‰Τ-γΤ ΥΥ)$Υ(NΥwΥ"�Υ€―Υ0ΦEΦKΦhΦ
}Φ ‹Φ*�Φ+ΓΦοΦφΦϋΦM�ΦMMΧ
›Χ©Χ °ΧΌΧ ΞΧ ΪΧηΧχΧΨ+ΨDΨcΨ‚Ψ
ΆΨ­Ψ.¶Ψ>εΨw$ΩQ�ΩΝξΩ+ΌΪθΪψΪ
Ϋ%-ΫVSΫ-�Ϋ)ΨΫά
άά#ά3ά!Oάqάƒά�ά •άΆά ±ά�Ύά@έ]έ
}έ�έ‘έ¥έΉέΟέζέώέή+ή?ήYήpή/�ή:Έή<σή0ίDίKίeί#ƒί§ί,Βί^οί)Nΰ'xΰ ΰ¨ΰΊΰ"Ύΰ…αΰgαmαtα�α�α ¶αΓα$ΪαW�α"WβHzβ"Γβ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>
<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>
<h5>Protocol and Port</h5>
<p>
2026-03-13 20:44:45 -03:00
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>
The "Not Source" option negates the selected source IP, network, or peer(s).
</p>
2026-11-17 16:03:37 -03:00
DNS servers pushed to peers.
<br>
Using the internal IP as primary DNS enables internal name resolution
and DNS filtering.
2026-03-18 11:24:10 -03:00
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.
Interval used to refresh WireGuard status information in the web UI.
Optional name used only for display in the web interface.
2026-03-15 17:31:19 -03:00
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.
<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,
your browser will show a security warning until the problem is fixed.
</div>
2026-02-09 22:07:48 -03:00
<h4>Authentication Types</h4>
<p>Select how users will authenticate through this method.</p>
<h5>Local Password</h5>
<p>Users will authenticate using a standard username and password stored locally. Only one of this type can be created.</p>
2025-12-29 18:30:39 -03:00
<h5>OIDC (OpenID Connect)</h5>
2026-03-12 18:54:37 -03:00
<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>
<p>Gatekeeper users are used for authenticating against protected applications managed by this gateway.</p>
<h5>Password</h5>
2026-03-13 20:44:45 -03:00
<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
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>
2026-11-20 21:58:17 -03:00
<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>
<h5>Wireguard Manager</h5>
<p>Authority to add, edit, and remove configurations of WireGuard instances.</p>
2026-03-12 18:54:37 -03:00
<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>
<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>
<h5>API Keys</h5>
<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>
2025-12-29 18:30:39 -03:00
<p><strong>Allowed Instances:</strong> The WireGuard instances this key can manage. If none are selected, the key has access to ALL instances.</p>
2026-01-16 15:01:13 -03:00
<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>
<h5>Primary Enable WireGuard</h5>
<p>Lists this primary server as an option when downloading peer configurations and VPN invites.</p>
2026-11-20 21:58:17 -03:00
<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>
<h5>WireGuard Instances</h5>
<p>All peers in this WireGuard instance can be managed by users with this peer group, including adding or removing peers.</p>
<h5>Routing Templates</h5>
2026-11-20 21:58:17 -03:00
<p>Define routing configurations that can be applied to peers.</p>
<h5>Default Template</h5>
<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>
2026-11-20 21:58:17 -03:00
<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>
<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>
<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>
2026-01-27 15:22:12 -03:00
</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: es
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=2; plural=(n != 1);
<h5>ConfiguraciΓ³n avanzada del firewall VPN</h5>
<p>
Esta interfaz sirve como una herramienta completa para gestionar reglas de firewall, permitiendo a los usuarios implementar polΓ­ticas de trΓ΅fico avanzadas entre peers de VPN y redes. Simplifica el establecimiento de reglas de firewall, el filtrado de paquetes y las configuraciones de NAT, posibilitando un control preciso de la seguridad de la red. Los usuarios pueden definir direcciones IP de origen y destino, puertos, protocolos y acciones para ajustar el flujo de trΓ΅fico, asegurando un entorno de red seguro y eficiente.
</p>
<h5>SelecciΓ³n de destino</h5>
<p>
Puedes aplicar esta regla a una direcciΓ³n IP o red especΓ­fica y/o a mΓΊltiples peers como destino.<br><br>
Habilitar "Include peer networks" incluirΓ΅ automΓ΅ticamente todas las IPs permitidas asociadas a cada peer seleccionado como destino.<br><br>
Ten en cuenta que seleccionar mΓΊltiples peers con redes incluidas tanto en origen como en destino puede incrementar rΓ΅pidamente el nΓΊmero de reglas generadas, dependiendo de tu configuraciΓ³n.<br><br>
La opciΓ³n "Not Destination" niega la IP, red o peer(s) seleccionado(s).
</p>
<h5>Protocolo y puerto</h5>
<p>
2026-03-13 20:44:45 -03:00
Solo se listan los protocolos mΓ΅s comunes. Si necesitas uno especΓ­fico, abre un issue en GitHub.<br><br>
Seleccionar TCP+UDP duplicarΓ΅ las reglas generadas.<br><br>
Puedes especificar puertos como nΓΊmeros individuales (por ejemplo, 8080) o rangos (por ejemplo, 8001:8999).
</p>
<h5>SelecciΓ³n de origen</h5>
<p>
Puedes aplicar esta regla a una direcciΓ³n IP o red especΓ­fica y/o a mΓΊltiples peers.<br><br>
Habilitar "Include peer networks" incluirΓ΅ automΓ΅ticamente todas las IPs permitidas asociadas a cada peer seleccionado.<br><br>
Ten en cuenta que seleccionar mΓΊltiples peers con redes incluidas tanto en origen como en destino puede incrementar rΓ΅pidamente el nΓΊmero de reglas generadas, dependiendo de tu configuraciΓ³n.<br><br>
La opciΓ³n "Not Source" niega la IP, red o peer(s) seleccionado(s).
</p>
2026-11-17 16:03:37 -03:00
Servidores DNS enviados a los pares.
<br>
El uso de la IP interna como DNS primario permite la resoluciΓ³n de nombres interna
y el filtrado de DNS.
2026-03-18 11:24:10 -03:00
Obliga as regras de roteamento definidas pelas modelos de roteamento usando regras de firewall.
<br>
Pares con una ruta predeterminada (0.0.0.0/0) no estΓ΅n restringidos.
<br><br>
Nota: dependiendo del nΓΊmero de rutas y pares, esta opciΓ³n puede generar
un gran nΓΊmero de reglas de firewall.
DirecciΓ³n IP interna y mΓ΅scara de red utilizadas por la interfaz WireGuard.
Intervalo utilizado para actualizar la informaciΓ³n de estado de WireGuard na interface web.
Nombre opcional utilizado solo para visualizaciΓ³n en la interfaz web.
2026-03-15 17:31:19 -03:00
Nombre de host pΓΊblico o direcciΓ³n IP y puerto UDP utilizados por los pares para conectarse.
<br>
El <b>Puerto de escucha</b> debe estar expuesta y mapeada en su archivo Docker compose (YAML).
Claves privada y pΓΊblica de WireGuard para esta interfaz.
<br>
La clave privada debe permanecer secreta.
Cambiarla requiere atualizar todas las configuraciones de los pares.
<h5>Puertos predeterminados</h5>
<p>El archivo <code>docker-compose.yml</code> predeterminado especifica el rango de puertos <b>TCP</b> <b>8080-8089</b>. Si deseas cambiarlo, edita manualmente el archivo <code>docker-compose.yml</code> y vuelve a ejecutar Docker Compose segΓΊn las <a href="https://github.com/eduardogsilva/wireguard_webadmin?tab=readme-ov-file#deployment">instrucciones de despliegue</a>.</p>
<h5>Tipo de destino: Peer</h5>
<p>La redirecciΓ³n de puerto darΓ΅ prioridad a la primera IP del peer con prioridad cero.</p>
<h5>Tipo de destino: DirecciΓ³n IP</h5>
<p>Las reglas redirigirΓ΅n al IP especificado. Recuerda asignar esa IP o red a un peer.</p>
<h5>AΓ±adir regla de reenvΓ­o</h5>
<p>Genera automΓ΅ticamente una regla de reenvΓ­o para ajustarse a configuraciones mΓ΅s estrictas de firewall.</p>
<h5>Enmascarar origen</h5>
<p>SoluciΓ³n temporal cuando un peer no usa la VPN como puerta predeterminada. No se recomienda: cambia la IP de origen de todas las conexiones por la de la instancia WireGuard.</p>
<h5>PolΓ­tica de denegaciΓ³n</h5>
<p>Una polΓ­tica de denegaciΓ³n bloquea todo el acceso a las rutas coincidentes.</p>
<h5>PolΓ­tica protegida</h5>
<p>Una polΓ­tica protegida requiere que los usuarios se autentiquen antes de acceder a la aplicaciΓ³n.</p>
<ul>
<li><strong>Grupos permitidos</strong>: Limita el acceso a grupos de usuarios especΓ­ficos. Nota: El uso de grupos requiere seleccionar un MΓ©todo de autenticaciΓ³n de tipo "ContraseΓ±a local".</li>
<li><strong>MΓ©todos de autenticaciΓ³n</strong>: Especifique quΓ© mΓ©todos pueden utilizar los usuarios para autenticarse (por ejemplo, ContraseΓ±a local, TOTP, OIDC).</li>
</ul>
<h5>PolΓ­tica pΓΊblica</h5>
<p>Una polΓ­tica pΓΊblica permite el acceso a la aplicaciΓ³n sin requerir ninguna autenticaciΓ³n.</p>
<div class="alert alert-warning">
Este hostname se utiliza para acceder a WireGuard WebAdmin. Si no se puede emitir el certificado,
su navegador mostrarΓ΅ una advertencia de seguridad hasta que se corrija el problema.
</div>
2026-02-09 22:07:48 -03:00
<h4>Tipos de AutenticaciΓ³n</h4>
<p>Seleccione cΓ³mo se autenticarΓ΅n los usuarios a travΓ©s de este mΓ©todo.</p>
<h5>ContraseΓ±a Local</h5>
<p>Los usuarios se autenticarΓ΅n utilizando un nombre de usuario y contraseΓ±a estΓ΅ndar almacenados localmente. Solo se puede crear uno de este tipo.</p>
2025-12-29 18:30:39 -03:00
<h5>OIDC (OpenID Connect)</h5>
2026-03-12 18:54:37 -03:00
<p>Los usuarios se autenticarΓ΅n a travΓ©s de un proveedor de identidad externo (como Keycloak o Google). Requiere URL del Proveedor, ID de Cliente y Secreto de Cliente.</p>
<h5>TOTP (ContraseΓ±a de un Solo Uso Basada en Tiempo)</h5>
<p>Los usuarios deberΓ΅n ingresar un token rotativo de una aplicaciΓ³n de autenticaciΓ³n. Si un usuario no tiene configurado un TOTP personal, se utilizarΓ΅ el <strong>Secreto TOTP Global</strong> en su lugar.</p>
<h4>Usuario de Gatekeeper</h4>
<p>Los usuarios de Gatekeeper se utilizan para autenticarse en aplicaciones protegidas gestionadas por este gateway.</p>
<h5>ContraseΓ±a</h5>
2026-03-13 20:44:45 -03:00
<p>Obligatorio al crear un usuario. Al editar, deje ambos campos de contraseΓ±a en blanco para mantener la contraseΓ±a actual.
Las contraseΓ±as se almacenan mediante el hash <strong>Argon2id</strong>.</p>
<h5>Secreto TOTP</h5>
<p>Secreto TOTP opcional por usuario. Cuando estΓ΅ configurado, este usuario se autenticarΓ΅ usando su propio secreto en lugar del
secreto TOTP global configurado en el MΓ©todo de AutenticaciΓ³n. Utilice los botones debajo del campo para generar un
secreto aleatorio y escanee el cΓ³digo QR con su aplicaciΓ³n de autenticaciΓ³n. Valide el secreto ingresando el PIN actual de
6 dΓ­gitos antes de guardar.</p>
2026-11-20 21:58:17 -03:00
<h4>Niveles de usuario</h4>
<h5>Analista de depuraciΓ³n</h5>
<p>Acceso a informaciΓ³n bΓ΅sica y registros para depuraciΓ³n. Sin permiso para modificar ajustes o ver datos sensibles como claves de peer.</p>
<h5>Solo lectura</h5>
<p>Acceso completo de visualizaciΓ³n, incluyendo claves y archivos de configuraciΓ³n. No puede modificar ajustes.</p>
<h5>Gestor de peers</h5>
<p>Permisos para aΓ±adir, editar y eliminar peers e IPs. No incluye modificar configuraciones de instancias WireGuard u otros ajustes.</p>
<h5>Gestor de WireGuard</h5>
<p>Autoridad para aΓ±adir, editar y eliminar configuraciones de instancias de WireGuard.</p>
2026-03-12 18:54:37 -03:00
<h5>Administrador</h5>
<p>Acceso total al sistema. Puede ver y modificar todas las configuraciones y gestionar usuarios.</p>
<br>
<h4>Grupos de peers</h4>
<p>Selecciona los grupos de peers a los que puede acceder este usuario. Si no seleccionas ninguno, tendrΓ΅ acceso a todos.</p>
<h4>Consola</h4>
<p>Habilitar o deshabilitar acceso a la consola web para este usuario.</p>
<h4>Filtro mejorado</h4>
<p>Este filtro muestra solo los peers a los que el usuario tiene acceso. SegΓΊn el tamaΓ±o de tu entorno, puede impactar rendimiento. Para mitigarlo, aumenta el "Intervalo de actualizaciΓ³n web" para reducir las solicitudes.</p>
<h5>Claves de API</h5>
<p>Las claves de API permiten que aplicaciones externas interactΓΊen com a API do WireGuard WebAdmin.</p>
<p><strong>Token:</strong> El token secreto utilizado para la autenticaciΓ³n. MantΓ©ngalo seguro.</p>
2025-12-29 18:30:39 -03:00
<p><strong>Instancias permitidas:</strong> Las instancias de WireGuard que esta clave puede gestionar. Si no se selecciona ninguna, la clave tiene acceso a TODAS las instancias.</p>
2026-01-16 15:01:13 -03:00
<p><strong>Permisos:</strong> acciones especΓ­ficas permitidas para esta clave.</p>
<h5>Ruta de AplicaciΓ³n</h5>
<p>Una Ruta define un prefijo de ruta dentro de esta AplicaciΓ³n que requiere una PolΓ­tica de Acceso especΓ­fica.</p>
<ul>
<li><strong>Nombre de la Ruta</strong>: Un identificador interno para esta ruta (ej: "public_api", "admin_area"). Se usa para referencias y exportaciones.</li>
<li><strong>Prefijo de Ruta</strong>: La ruta de la URL que activa esta ruta (ej: <code>/api/</code> o <code>/admin/</code>). Use <code>/</code> para coincidir con todas las rutas restantes.</li>
<li><strong>PolΓ­tica</strong>: La PolΓ­tica de Acceso que se aplicarΓ΅ cuando un usuario acceda a esta ruta.</li>
<li><strong>Orden</strong>: Determina la prioridad de esta ruta al evaluar la solicitud. Los nΓΊmeros mΓ΅s bajos se evalΓΊan primero. Si varias rutas coinciden con una ruta, gana la de menor orden.</li>
</ul>
<h5>AplicaciΓ³n</h5>
<p>Defina los detalles principales de la aplicaciΓ³n que desea exponer a travΓ©s del gateway.</p>
<ul>
<li><strong>Nombre</strong>: Un identificador interno ΓΊnico para esta aplicaciΓ³n (ej: "wiki", "crm"). Contiene solo letras, nΓΊmeros, guiones o guiones bajos.</li>
<li><strong>Nombre para mostrar</strong>: Un nombre amigable y legible para fines de visualizaciΓ³n.</li>
<li><strong>Upstream</strong>: La URL de destino a la que se reenviarΓ΅n las solicitudes (ej: <code>http://10.188.18.27:3000</code>). Debe comenzar con <code>http://</code> o <code>https://</code>.</li>
</ul>
<h5>Cluster habilitado</h5>
<p>Cuando estΓ΅ deshabilitado, los workers son rechazados y apagan sus interfaces WireGuard, y las aplicaciones del App Gateway solo las publica este servidor primario. Requiere la cachΓ© de estado de WireGuard.</p>
<h5>Habilitar WireGuard primario</h5>
<p>Muestra este servidor primario como opciΓ³n al descargar configuraciones de peer e invitaciones de VPN.</p>
2026-11-20 21:58:17 -03:00
<h5>Modo de cluster</h5>
<p><strong>Mirror</strong>: todos los workers reciben las mismas instancias de WireGuard, peers, firewall y configuraciΓ³n de DNS. Los peers pueden conectarse a cualquier servidor.</p>
<p><strong>Distributed</strong>: cada instancia de WireGuard se ejecuta solo en el servidor seleccionado en la configuraciΓ³n de la instancia (el servidor primario por defecto). Los peers se conectan a ese servidor. Las reglas de firewall no pueden vincularse a la interfaz de una instancia especΓ­fica: use wg+ o direcciones IP. DespuΓ©s de cambiar el modo, aplique la configuraciΓ³n de WireGuard para que el servidor primario detenga las instancias que pasaron a los workers.</p>
<h5>VisualizaciΓ³n del worker</h5>
<p>CΓ³mo se nombran los workers en las selecciones de servidor (descargas de configuraciones de peer e invitaciones de VPN).</p>
<h5>Lista de Direcciones IP</h5>
<p>Administre direcciones IP o redes especΓ­ficas a las que se les permite o deniega el acceso al usar el mΓ©todo de autenticaciΓ³n por Lista de Direcciones IP.</p>
<h5>DirecciΓ³n IP y Prefijo</h5>
<p>Ingrese una ΓΊnica direcciΓ³n IP (ej: 192.168.1.50) o una direcciΓ³n de red. Use la longitud del prefijo para la notaciΓ³n CIDR (ej: 24 para una red /24). Deixe el prefijo en blanco para un ΓΊnico host (/32 para IPv4, /128 para IPv6).</p>
<h5>AcciΓ³n</h5>
<p><strong>Permitir</strong>: Otorga acceso a la red/IP especificada.<br>
<strong>Denegar</strong>: Bloqueia especificamente el acceso desde la red/IP especificada.</p>
<h5>DescripciΓ³n</h5>
<p>Una nota opcional para ayudar a identificar esta entrada (ej: "Red de la Oficina", "Atacante Bloqueado").</p>
<h5>Peers</h5>
<p>Selecciona los peers que pueden gestionar los usuarios de este grupo.</p>
<h5>Instancias de WireGuard</h5>
<p>Todos los peers en esta instancia de WireGuard pueden ser gestionados por usuarios de este grupo, incluyendo aΓ±adir o eliminar peers.</p>
<h5>Plantillas de Enrutamiento</h5>
2026-11-20 21:58:17 -03:00
<p>Defina configuraciones de enrutamiento que se pueden aplicar a los pares.</p>
<h5>Plantilla Predeterminada</h5>
<p>Si estΓ΅ marcado, esta plantilla serΓ΅ la predeterminada para la instancia WireGuard seleccionada. Solo se permite una plantilla predeterminada por instancia.</p>
<h5>Tipo de Ruta</h5>
2026-11-20 21:58:17 -03:00
<p>Seleccione el tipo de rutas para enviar al cliente.</p>