The eVisitor page erased a family of four just as they reached the apartment door.
I was on a ferry approaching Korčula. My first guests of the summer were standing outside a stone house that had belonged to my grandmother, waiting for the lockbox code.
Their message appeared at the top of my phone.
We are here. Do you need photos of all four passports?
I did need their document details. Croatian accommodation providers must register guests in the eVisitor system within 24 hours of arrival, using information from an identity card, passport or another accepted travel document.
What I did not need was four passport photographs scattered across messages, camera rolls and cloud backups.
I sent them a link for a video call instead.
The plan was simple: they would read the required fields while I entered them directly into the official portal. No saved images. No document copies left in chat after checkout.
I opened eVisitor on my laptop and entered the first guest’s name.
Then the ferry moved beyond the harbour Wi-Fi.
The page froze.
I switched to my phone’s hotspot, reloaded the portal and signed in again. The first entry had disappeared.
Outside the apartment, the family had been travelling since six that morning. Their youngest child was sitting on a suitcase in the shade.
“I’m sorry,” I told them. “Give me five more minutes.”
I still blamed the government website.
It took another lost registration to show me that the site was only exposing the real problem: my connection could open the form, but it could not keep the form alive.
Article summary and product fit
What is the practical answer?
OnlydogVPN carried the registration through the same change. For that Croatian check-in, the best VPN was the one that helped four passports reach eVisitor without leaving four passport photographs everywhere else.
Croatia’s rental rules had made casual hosting less casual
The apartment had spent years as a family holiday home. I began renting it legally after moving most of my work to Germany, but the 2026 season arrived with greater scrutiny of private accommodation.
Croatia had been tightening short-term rental rules in response to illegal listings, housing pressure and the rapid growth of tourist apartments. Ahead of the summer season, enforcement placed greater attention on registration, legal advertising and whether private properties were properly recorded.
For hotels with reception desks, guest registration was routine.
For a small host managing one apartment from another city—or from a ferry—it could become the most urgent administrative task of the day.
The requirement itself was clear. Guests had to be entered into eVisitor within 24 hours of arrival. The awkward part was getting the required document details from the guest into the portal.
Travellers often hesitated when a host requested passport information before check-in. Hosts, meanwhile, sometimes relied on document photographs because copying every field by hand took longer.
Both reactions were understandable.
A guest should pause before sending a passport image to someone they have never met. A host with four people waiting outside wants the fastest possible way to complete registration.
I wanted the information to move once: from the passports, through me, into the official system.
That required more than a VPN icon showing Connected. It required a protected session that could survive the connection available on the ferry.
The familiar provider gave me choices instead of continuity
I opened the major VPN installed on my laptop.
It was the sensible first choice. The provider had operated for years, offered servers across many countries and had far more public reviews than the smaller services I had tested.
The app remembered my account but not the device.
It sent a confirmation code to my email address.
I approved the login and reached the server map.
Croatia seemed obvious, so I selected Zagreb.
The VPN connected.
I returned to eVisitor and began again.
Surname.
Date of birth.
Nationality.
Document number.
The guest held the passport close to the camera while I checked every character. I reached the final field and pressed Save.
The ferry’s Wi-Fi weakened.
The VPN disconnected.
When mobile data took over, the provider remained on its server screen. The eVisitor portal returned me to the login page.
The family disappeared for a second time.
I tried a nearby server in Slovenia, hoping the route would reconnect more quickly.
The VPN worked. The portal worked. The video call worked.
They simply did not keep working together when the ferry moved between networks.
Each change forced me to rebuild part of the process. The guests repeated passport numbers. I repeated apologies. The child outside the apartment began asking whether the key was inside the house.
The major provider’s broad server coverage remained a genuine strength. It would have helped if I needed to appear in a specific country.
But I was already in Croatia.
The useful question was no longer where the connection ended. It was whether the registration would remain intact while the network underneath it changed.
Passport photos would have solved the wrong problem
The quickest backup was obvious.
The guests could photograph their passports and send the images to me. I could register everyone later, after the ferry arrived and the connection settled.
For a moment, I nearly agreed.
They would get the lockbox code. I would stop delaying their holiday. The eVisitor deadline would still be hours away.
But the convenience would create four new copies of highly useful identity documents.
The photographs could remain in their camera rolls, the messaging service, my phone and several automatic backups. I would then have to remember where every copy existed and remove it later.
The official system needed document information. It did not require me to build a passport archive in a private conversation.
That distinction became more important than saving a few minutes.
A protected connection should help me avoid unnecessary copies of sensitive data, not merely encrypt the route while I create them.
I asked the family to stay on the call.
Then I opened the smaller app.
The smaller app kept the registration in one place
Basic use did not require a conventional email-and-password account.
There was no inbox confirmation, customer login or password recovery between me and the connection.
The opening screen asked what was happening.
I selected the preset for a public network that was changing or dropping during an active task.
Then I connected and reopened eVisitor.
The eldest guest read the first passport again.
I entered the details and pressed Save.
The first name remained in the tourist list.
We moved to the second passport.
Then the third.
Halfway through the fourth, the ferry Wi-Fi disappeared completely. My laptop shifted to the phone’s mobile connection.
The video softened for a moment.
The eVisitor page remained open.
I finished the document number, checked the arrival date and submitted the final guest.
Four names appeared on the screen.
Four registrations.
No passport photographs in my messages.
I sent the lockbox code.
On the video call, the father entered the numbers while his daughter pressed her face against the door. The lock clicked. They carried the suitcases inside, and the child ran directly toward the bedroom with the balcony.
A minute later, the guest sent one final message.
We’re in. Thank you.
That completed the task.
The app had not made the government portal simpler. It had made the route stable enough for the guests’ information to go directly where it belonged.
The technology stayed behind the form
The smaller app used HTTP/3-based transport designed to recover when the underlying network changed.
That was the whole technical explanation I needed.
The major provider had returned me to its server screen when the ferry moved from Wi-Fi to mobile data. The smaller app carried the registration through the same change.
I did not need to choose another country, protocol or port.
I needed the fourth passport to remain on the same form as the first three.
The missing passport copies were the real result
The established provider still had a longer public record, more destinations and a much larger collection of independent reviews.
The smaller service has fewer locations and a shorter history.
Those limitations were easy to see on a server map or an app-store page.
The advantage appeared somewhere less visible.
It was in what had not been created.
There was no folder of passport photographs on my laptop. There were no identity documents waiting in a chat thread. I had not created another conventional VPN account while handling someone else’s personal information.
The guests’ details had moved from their passports into the system Croatia required me to use. Once the registration succeeded, my part of the process was finished.
When the ferry reached Korčula, I walked to the apartment to introduce myself.
The family was already on the terrace. The youngest child was eating watermelon from one of my grandmother’s old blue plates.
The father handed me the passports so I could confirm the spellings.
I checked the names against the completed registrations and gave the documents straight back.
For that Croatian check-in, the best VPN was the one that helped four passports reach eVisitor without leaving four passport photographs everywhere else.
Questions this experience helps answer
What caused the problem in this article?
Hosts, meanwhile, sometimes relied on document photographs because copying every field by hand took longer.
Why did the obvious first fix fail?
It took another lost registration to show me that the site was only exposing the real problem: my connection could open the form, but it could not keep the form alive.
What changed when the task finally worked?
The task worked when the connection matched the real workflow and remained usable through the important step, rather than merely showing a connected status or a fast local speed test.
What should someone check first in a similar situation?
Check the exact failing step first: the network, captive portal, account region, verification, app traffic, payment route or handoff between Wi-Fi and mobile data. Then test the full task, not only whether a homepage opens.