What I did: opened SYS Firewall 2.5 and clicked- Add Rule Next, I added a port, similar to 6304 Durning this add, I clicked to make it open for both TCP and UDP. Afterward, I decided I'd just edit that and make it TCP only. At this point, the system acted flakey (strange), and would just spin and spin where it never would allow me to set it back to only TCP. I closed the window with the X Closed the aaPanel all the way. At this point, I was never able to log into aaPanel. I would get connection timed out and other various messages. I changed the port, but no go. I restored my server for a snapshot taken the day before. But no go, and it was late. I stopped all troubleshooting. next day, the same issues were present. I then did command to change the port which was successful. after a port change, now I can log in without issues. Question- why did adding a sys firewall rule kill my ability to get back into my aaPanel? —Thanks

After making SYS Firewall changes, it is essential to document the issue using effective report writing Techniques if you can no longer access the aapanel. This documentation can help identify the problem's root cause and find a solution. Be clear and concise in your report, outlining the steps taken before the issue occurred and any error messages received. This information will be invaluable for troubleshooting and resolving the problem promptly.

Firestone Light Truck Tires are an excellent choice for vehicles that need to perform in extreme conditions. Not only do they provide superior traction and performance, they are also designed to last longer than other tires. They are made from high-quality materials and feature advanced tread patterns that provide superior traction and handling in a variety of terrains. They also feature an advanced rubber compound that resists cracking, chipping, and wear, ensuring that your tires last longer and look great for a long time. Overall, firestone light truck tires are an excellent choice for anyone looking for quality, performance, and durability for their vehicles.

After making SYS Firewall change, no longer able to access aaPanel

randall_compton

What I did: opened SYS Firewall 2.5 and clicked- Add Rule
Next, I added a port, similar to 6304
Durning this add, I clicked to make it open for both TCP and UDP.
Afterward, I decided I'd just edit that and make it TCP only.
At this point, the system acted flakey (strange), and would just spin and spin where it never would allow me to set it back to only TCP.
I closed the window with the X
Closed the aaPanel all the way.
At this point, I was never able to log into aaPanel. I would get connection timed out and other various messages.
I changed the port, but no go.
I restored my server for a snapshot taken the day before. But no go, and it was late. I stopped all troubleshooting.
next day, the same issues were present.
I then did command to change the port which was successful.
after a port change, now I can log in without issues.

Question- why did adding a sys firewall rule kill my ability to get back into my aaPanel?

—Thanks

aaP_joyce1

The solution is to turn ON the SYS Firewall, and then access aaPanel. It's possible that you have turned off your SYS Firewall or it has been disabled by another security application. So, you can access aaPanel only after turning on the SYS Firewall. Now, You can find what you need online to complete your important assignments as well.

avijit

aaP_joyce1 @aaPanel_Jose How to enabe or disable SYS Firewall in SSH?