Astronomy Server Migration & Camera FTP

@farooqtahir2013

With over a decade in the field of information technology, I possess comprehensive knowledge and skills that make me the ideal candidate for your astronomy server migration project. My deep expertise in network administration, system administration, and my substantial experience with Windows servers is particularly relevant to your needs. I have successfully designed and implemented network infrastructure for various-sized companies including enterprises, adhering to the best practices of renowned vendors such as Cisco, Microsoft, and VMware - to name a few. In addition to my technical proficiency, I'm well-known for providing prompt responses and 24-hour availability. As we all know, timing is crucial in any task; a slight delay could hamper your telescope operations. But with me on board, running your project efficiently within the given time-frame is guaranteed. Together we can ensure that Server #2 is fully functional with both cameras writing data without interruption while retaining access to your weather system on Server #1 (or alternative access if needed)—all without any manual intervention on your part.

@AZTURK1

Hi there, I see you've got the All Sky Camera and Skypi RO Seeing needing FTP uploads to Server #2, and that WinSCP credential recovery is blocking you on skypionline.com. I can get both cameras reliably transferring frames and secure Server #2 so you're not left hanging when the old webmaster's setup breaks. What I'll do: ✅ Deploy and harden Server #2 with RDP locked down, firewall rules tight, and a clean FTP/SFTP service configured for your Starlight Express and QHYCCD5 II. ✅ Set up scheduled tasks or a lightweight automation script to keep those camera uploads running 24/7—no manual intervention. ✅ Resolve the WinSCP credential issue—either recover it if possible or replace the workflow with a documented alternative that gives you the same live feed and logging. ✅ Leave Server #1 weather station reachable and provide a full handoff doc with credentials, paths, and any new scheduled tasks. Skills: ✅ 7+ years Windows Server administration—RDP hardening, firewall, and automation. ✅ Network security and FTP/SFTP configuration for production camera workflows. ✅ WinSCP credential recovery and automation scripting. ✅ Microsoft® Certified: MCSA | MCSE | MCT. ✅ 300+ projects delivered, 280+ five-star reviews. Why me: I can start immediately and I've handled similar remote-access setups where automation and reliability are critical—no babysitting the cameras overnight.

@sedawy

As a seasoned DevOps and Cloud engineer with over 15 years' experience in IT infrastructure, I'm confident I possess the set of skills necessary to tackle your challenging remote-access astronomy project. My deep expertise in deploying cloud solutions such as AWS, Azure, and GCP perfectly aligns with your need for migrating from an aging Server #1 to a new Windows machine (Server #2). Additionally, I have ample experience in setting up CI/CD pipelines using Jenkins, GitHub Actions, and GitLab CI, which will be instrumental in ensuring consistent FTP transfers from your Starlight Express and QHYCCD5 II cameras to Server #2. Furthermore, as an experienced Python developer, I can leverage this language's automation capabilities to develop bespoke solutions specific to your recovery of lost credentials or entire replacement workflow issue. Lastly, my qualifications extend beyond technical prowess — with an MBA in E-Business, I understand the fundamental importance of aligning IT operations with overall business needs. This not only means timely turnarounds but also well-documented procedures that facilitate easy hand-offs. With my dedication to providing secure, scalable solutions and ensuring your systems are faster, safer, and smarter, I believe I can add significant value to your project. Let's start bringing clarity back into your astronomy setup.

@shakilan4

Hi, I can handle the migration from Server #1 to Server #2, including Windows Server hardening, RDP security, FTP/SFTP automation for the All Sky Camera and Skypi RO Seeing, and scheduled transfers with logging. I can also replace the old WinSCP workflow if credential recovery isn’t possible while keeping the remaining weather services on Server #1. I’ll provide a clear handover document with paths, ports, tasks, and configuration details. Ready to start quickly.

@codefusion53

Hi I can handle the migration from Server #1 to Server #2 while keeping the existing weather services operational and minimizing disruption to your WordPress-based sky conditions page. I’ll first audit the current Windows services, scheduled tasks, WinSCP/FTP configuration, camera output paths, and website transfer workflow. I can then move the All Sky Camera and Skypi RO Seeing image transfers to Server #2 while leaving the remaining weather data on Server #1. For the missing WinSCP credentials, I’ll check whether the existing configuration can be legitimately recovered from the server/account. If not, I’ll establish a clean replacement using new credentials, automated SFTP/FTP transfers, logging, retries, and scheduled tasks. I’ll also configure and harden Server #2, verify RDP access, test both camera feeds end-to-end, and provide a handover document covering paths, ports, tasks, scripts, and credentials. I can prioritize this for a quick turnaround once remote access is available. Best, Justin

@AndrewJSMAN

I've handled Windows Server migrations with hardware integration and credential recovery before, so this is right in my wheelhouse. I'll harden Server #2 with RDP lockdown and proper FTP/SFTP service config, then set up automated upload workflows for both your Starlight Express and QHYCCD5 II cameras to their designated folders without manual intervention. For the WinSCP credentials—I'll attempt recovery from the old config files first; if that fails, I'll build a clean replacement using either WinSCP with scheduled tasks or a lighter alternative like FileZilla with batch scripting, depending on your logging and automation needs. I'll keep your weather station live on Server #1 throughout the cutover, validate both camera streams are writing reliably, and hand off a document with all connection details, FTP paths, and any scheduled tasks I set up. I can start immediately. Thanks, Andrii.

@venplura

I've done a fair bit of Windows Server setup and astronomy camera automation, so the core of this—moving your imaging pipeline to Server #2 while keeping weather accessible on Server #1—sits squarely in my wheelhouse. My approach: get Server #2 hardened and RDP-ready first, then configure FTP credentials and folder permissions for both the Starlight Express and QHYCCD5 II. For the WinSCP question, I'd likely recommend moving to a script-based solution (batch or PowerShell) once we recover or reset those credentials—gives you better logging and scheduling than the GUI alone. The tricky bit is keeping that live-weather feed running on Server #1 without manual intervention; I'd handle that by either recovering the old WinSCP config or rebuilding the connection cleanly and documenting it all in a handoff doc with ports, paths, and any scheduled tasks. I can turn this around quickly and deliver everything you listed: Server #2 online, both cameras writing reliably, weather still live, and a full credential + connection summary. If that sounds like the right fit, happy to dig into more specifics. Corné

@Hrolgar

WinSCP saved sessions store the password in a weak, reversible obfuscation keyed to the Windows profile that saved them. Before touching Server #1 I'd pull that entry and run it through a decryptor, if the profile's intact it's usually a five minute recovery rather than a rebuild. Either way, the real work is a hardened SFTP service on Server #2, one account per camera, key based auth, each chrooted to its own upload folder. Re-pointing the Starlight Express and QHYCCD5 II usually isn't a setting in the capture software itself, it's whatever script or task actually pushes the files, so I'd find that on Server #1 first rather than guess at config. The weather feed stays live on Server #1 through the whole cutover, everything else gets pulled off in sequence. M1: hardened SFTP on Server #2 stood up, weather feed confirmed unaffected, WinSCP recovery attempted, $211, 2 days. M2: both cameras re-pointed, uploads verified landing, scheduled tasks rebuilt, $250, 2 days. M3: Server #1 decommissioned except the weather feed, written handoff of credentials, paths and tasks, $177, 1 day. Is the weather feed its own service on Server #1 or just a script, and does anything else read from that host? Are the camera uploads triggered by the capture software directly or a separate scheduled job I should check first?

@edwarddzi8f

Hi there, I can help you with this astronomy server migration. The trickiest part will be replicating that WinSCP workflow without the old credentials, but I can set up a clean SFTP solution on Server #2 with scheduled tasks that handle both cameras reliably and log everything. I'm Edward and I've done quite a few Windows Server migrations. I'd also lock down RDP access while I'm in there. Happy to chat about the details.

@Eliteinno

The main task is to transition telescope operations to a new Windows server while maintaining weather services on the old one. Configuring FTP or SFTP for the Starlight Express and QHYCCD5 II cameras is straightforward, though I recommend SFTP for enhanced security. We'll need a new workflow for the weather feed, given the missing WinSCP credentials. I can advise on the best client for automation and logging. Can you confirm if there are any existing scripts or automation tasks on Server #1 that need to be transferred or adapted to Server #2?

@adembuyukozer

I am computer engineer. I am Microsoft Certified Trainer for 12 years. I can help you.

@mikes126

I’ll migrate the two astronomy camera FTP workflows to Server #2 while keeping all other weather services running on Server #1, so the live-weather feed remains uninterrupted. I’ll first audit Server #1, identify the existing FTP/WinSCP paths, scheduled tasks, camera upload settings, WordPress integration, firewall rules, and dependencies before changing anything. I’ll harden Server #2, configure RDP securely, install the required Starlight Express and QHYCCD5 II drivers/software, create isolated upload folders and accounts, and configure FTP/SFTP with least-privilege permissions. If the old WinSCP credentials cannot be recovered legitimately, I’ll replace them with a clean SFTP/FTP workflow rather than risking the existing weather system. I’ll configure automated transfers, logging, retries, and monitoring so camera uploads continue without manual intervention. I’ll test both “All Sky Camera” and “Skypi RO Seeing” uploads end-to-end, verify WordPress can access the expected files, and confirm Server #1’s remaining weather services are unaffected. I’ll provide a hand-off document containing server/IP details, ports, folder paths, account/credential information, scheduled tasks, scripts, backup/recovery notes, and troubleshooting steps.

@jonasdedzo

Hi there, I understand the main goal is to migrate the two astronomy camera feeds to Server #2 while keeping the remaining weather services running on Server #1, with reliable automated transfers and secure remote access. I’d configure and harden Server #2, establish the correct FTP/SFTP workflow for the All Sky Camera and Skypi RO Seeing feeds, verify folder permissions and scheduled automation, and replace the missing WinSCP workflow if credential recovery isn’t practical. I’ll test continuous uploads, preserve the existing WordPress weather integration, document ports/paths/configuration, and ensure Server #1 remains untouched for the other weather services. I think you want a clean migration without disrupting the working weather system, rather than simply moving files between servers. I can approach it with reliability, security, and easy future maintenance in mind. Looking forward to work with you. Thanks

@novatech2210

Hello! I've been recommended by a Freelancer Recruiter. Nice to meet you. Your main requirement is a working delivery that matches the brief without breaking what you already have. I’ll start from your title and description, list the must-have requirements, and implement against your specified stack. Existing code and integrations stay in place unless you asked to replace them. I’ll confirm edge cases, errors, and acceptance checks before calling it done. The main technical risk is a mismatch between the listing and the live system. I’d first read the current flow and reproduce the reported behavior, then implement the smallest change that meets the written requirements and add a rollback path if the change has to be reversed. I'd love to chat about your project! The worst that can happen is you walk away with a free consultation. Regards, Chris | Lead Developer | Novatech

@razmiks2

Hi, I’ve migrated mission-critical Windows server workloads and automated file-transfer pipelines with reliable logging. You need Server #2 secured for RDP, cameras uploading frames via FTP/SFTP into fixed folders, and a weather feed that stays reachable on Server #1. I’ll harden the Windows setup, set up the transfer workflow, and ensure scheduled tasks keep it running through credential recovery or a clean replacement. I deliver dependable migrations with clear hand-off docs for connection details, ports, and scripts. Best, Razmik

@elijahhmonreal

Hi there, I reviewed your project requirements and I am interested in working with you. I have extensive experience delivering Troubleshooting, Automation, Network Monitoring, Data Backup, Database Management, Security Auditing, Windows Server, Data Recovery, Network Security and System Admin. I focus on understanding the requirements clearly, providing a practical solution, and delivering accurate, well-documented work on schedule. I am available to begin immediately and would be glad to discuss the scope, timeline, and budget. Best regards, Elijah M.

@sufyanasmat38

Drawing from my extensive experience and stellar team at Fourge, I believe we're the best fit for your astronomy server migration and camera FTP needs. Besides being adept in automation and database management - skills that will be pivotal in ensuring a smooth transition from Server #1 to #2, I can also bring valuable Windows Server hardening knowledge to the table. Ultimately, our work isn't just about meeting project briefs but building robust technology tailored to your precise needs. Allow Fourge to deliver a swift, secure server migration escalating your telescopic operations to new heights while keeping the weather station functional throughout. Excited to be part of your astronomy journey!

@nadiiai

Hello there, The real challenge here is not just moving the cameras to Server #2, but preserving the live weather feed from Server #1 while securely replacing the lost FTP credentials with a clean, auditable workflow—likely SFTP with key-based authentication—so both cameras upload reliably without breaking the existing WordPress integration. I will configure Server #2 with the necessary FTP or SFTP server, create dedicated folders for each camera, and set up automated upload scripts or scheduled tasks to handle the transfers from the imaging cameras, while keeping the weather station services running on Server #1 until the credential issue is resolved or we fully migrate that feed. I will also document every new credential, port, script, and scheduled task, and provide recommendations on hardening Server #2, ensuring the entire setup is secure and maintainable for the long term. I can complete the full migration and configuration within 2 to 3 days, and I will test each camera upload and the weather display before calling the job complete. Nadiia

@Cruz1217

The FTP upload from the Starlight Express and QHYCCD5 II often stalls when the new Windows server blocks passive mode connections. I'll reconfigure FTP to force passive mode, open the needed ports, and add a scheduled task that moves files to the right folders. You’ll see continuous image flow with no manual steps. A common mistake is keeping the old WinSCP profile after a server swap, which leaves stored passwords out of sync and breaks automation. I'll replace it with a fresh script that logs each transfer and add a firewall rule so the weather station stays reachable on Server 1. The hand‑off doc will list all new credentials, ports, and scheduled tasks for easy future maintenance.