Budget: 2000 UAH Deadline: 7 days
Hello, I have been working on setting up server security for an e-commerce project with over 50,000 products, where geographic traffic was blocked and automatic backups were configured with 99.9% uptime.
I am curious if you plan to use GeoIP blocking through nginx or better through iptables to block China/Singapore?
I suggest we get in touch, I will consult you for free on the technical side and we will create a development plan + I will tell you about my team!
Budget: 3000 UAH Deadline: 1 day
I will do it! Extensive experience in configuring website and server security. Write to me privately!
Budget: 7500 UAH Deadline: 14 days
Good day!
We are the SDEV team, specializing in system development and DevOps enhancements for web projects. We have experience working with dedicated Hetzner servers, security configuration, automation, and monitoring.
Regarding your task — we are ready to perform all technical tasks comprehensively:
1. We will block traffic from China and Singapore at the server level through geo-filtering in Nginx or using iptables. We will provide a detailed report with the rules used and instructions for further maintenance.
2. We will set up a cron job for daily product imports at 12:00. We will check the logs, the stability of the task, and add basic logging of execution.
3. We will conduct an audit of current backups: we will determine their schedule, volume, storage location (locally or on external storage), and check the possibility of restoration. If necessary, we will optimize the process.
4. We will add uptime monitoring with notifications about site downtime. We will set up notifications via email, and we can also implement integration with Telegram if needed.
5. We will implement basic bot protection:
- Filtering suspicious User-Agents.
- Rate limiting (limiting requests from a single IP address).
- Logging all blocks for further analysis.
- We guarantee that genuine users will not be affected.
All changes will be made cautiously, with prior backup of configurations. After completion, we will provide a report describing the implemented rules and recommendations for further maintenance.
An example of our similar case: Automotive search and monitoring — A complex bot for automated searching and monitoring of cars on various platforms with instant notifications.
Proposals concealed
Proposals are currently absent
Current freelance projects in the category DevOps
Updating and migrating Laravel projects to a new server
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.