Budget: 5000 UAH Deadline: 2 days
Hello. There is a solution to protect against DDoS attacks. We can discuss the details.
We have a server on the Keitaro tracker, but recently we have been facing massive DDoS attacks. Bots have started to send大量 to our links, clicking on them, which leads to system overload. Because of this, our Keitaro tracker stops working. We urgently need help implementing protection against such attacks, including bot filtering and stabilizing the tracker’s operation.
Budget: 5000 UAH Deadline: 2 days
Hello. There is a solution to protect against DDoS attacks. We can discuss the details.
Budget: 5000 UAH Deadline: 2 days
Contact me - I will do my best. We will repel the attack. We can start right now.
But from my experience - fighting bots and generally "parasitic traffic" is an ongoing process, so I would suggest ongoing support (we can discuss if interested). I have my own layered protection system, with minimal load on the server and which has been showing quite effective results for years on other servers.
Over 20 years of administration experience.
Examples of clients for whom I have configured and maintained servers can be viewed on my website and in my portfolio on this platform.
If desired, work can be done under a contract with payment to a bank account (I am a sole proprietor of group 3).
For clients with UBD status and their families, a 15% discount on all services.
30% of the earnings from this rate will be transferred to help the Armed Forces of Ukraine.
Budget: 5000 UAH Deadline: 4 days
Good day! My name is Margo.
I have experience in protecting web resources from DDoS attacks, particularly on Keitaro trackers.
I am ready to help with:
- configuring bot filtering (via WAF, reCAPTCHA, Cloudflare, iptables);
- optimizing and limiting server load;
- stabilizing Keitaro tracker operation under load;
- implementing bypass mechanisms (redirects, cloaking, etc. — if needed).
Cost: from 4,500 UAH (depends on access level and infrastructure).
I am ready to connect immediately after clarifying the details.
Budget: 5000 UAH Deadline: 7 days
Good day!
I can suggest connecting CloudFlare if the attack is targeting the domain and not the server's IP address. Monitoring and diagnostics are needed. If you're interested in the offer - contact me.
Budget: 5000 UAH Deadline: 1 day
, good day, I am interested in your task. I can set up DDoS protection for you
Budget: 5000 UAH Deadline: 5 days
Good day, very familiar with your tracker, installed overload protection, optimize requests, block unnecessary bots, if relevant, write in private message
Budget: 5000 UAH Deadline: 2 days
I will do this work for you,.
I will advise on how to avoid such threats in the future.
Budget: 5000 UAH Deadline: 2 days
Good day.
System administrator with over 7 years of experience.
Need to migrate the tracker to Cloudflare and set up blocking of malicious bots and accept traffic only from Cloudflare, I can set up everything, write in private.
Budget: 5000 UAH Deadline: 2 days
Hello!
Ready to help with implementing Keitaro protection against DDoS attacks and bot traffic. I have experience in setting up filtering.
Can provide reliable protection.
Contact me.
Budget: 5000 UAH Deadline: 1 day
Good day! I have some experience in this field!!!! Feel free to contact me, I will try to help you!!!!
It is necessary to perform the update, transfer, and configuration of Laravel projects to a new server, ensuring stable operation, security, protection against exploits, and correct functioning of all services after migration. 1. Main tasks Prepare the new server for operation. Transfer project files, databases, configurations, and cron jobs. Update server software. Configure a secure environment for Laravel. Check compatibility of PHP, Laravel, Composer packages, and dependencies. Ensure protection against known exploits, malicious requests, and unauthorized access. Set up SSL certificates. Check the functionality of the websites after the transfer. 2. Transfer of Laravel projects For each project, it is necessary to: Transfer project files. Transfer the database. Transfer the .env configuration. Set directory access permissions: storage bootstrap/cache Check functionality: homepage; admin panel; authorization; forms; API; file uploads; email sending; cron jobs; queue workers.3. Security and protection It is necessary to implement basic and application-level protection: close root access via SSH; configure SSH access only via keys; change the default SSH port if necessary; configure the firewall; allow only necessary ports; install Fail2Ban; hide service versions of Nginx/Apache/PHP; restrict access to .env, .git, backup files, log files; set correct file permissions; check projects for malicious files; check Composer packages for known vulnerabilities; update dependencies if it does not break functionality; configure protection against SQL injection, XSS, CSRF, and path traversal; check the correctness of Laravel APP_ENV and APP_DEBUG; set APP_DEBUG=false in production; configure rate limiting for critical endpoints; check access to storage/uploads; configure protection against PHP execution in upload directories; check access rights to admin panels. 4. SSL and domains It is necessary to: Install SSL certificates. Configure automatic SSL renewal. Enable redirect from HTTP to HTTPS. Check the correct operation of websites via HTTPS. 5. Backup It is necessary to configure backup: project files; databases; .env files; uploaded media; cron configurations; Nginx/Apache configurations. Backup should be performed automatically on a schedule. It is preferable to store copies separately from the main server. 6. Post-transfer verification After migration, it is necessary to check: absence of 500/403/404 errors; absence of critical errors in Laravel logs. 9. Result of execution After the work is completed, there should be: Laravel projects successfully transferred to the new server; websites are functioning stably; SSL is configured; the server is protected with basic security settings; access to critical files is restricted; backup is configured; cron and queues are operational; the old server can be turned off after final verification.
We have a dedicated server on Hetzner with a website on Docker (+ Laravel framework) Contact with the developers has been lost Need to: - restore and change server access (probably SSH) - recommend a storage location and set up a full server backup with easy recovery, probably not on Hetzner for security - fix the logo that is not displaying for some reason (it's unclear why the file has become inaccessible) Important - there is no website backup, and there is no room for error. We will only consider experienced specialists.