SES.HOSPEDAJES Not Working: Causes and Fixes

Guests are checking in today, the 24-hour clock is running, and SES.HOSPEDAJES won’t respond. It never happens during a quiet afternoon.

The ambiguity is not an accident. A service outage, an expired certificate, a browser with a stale cache and a submission password carrying an accent all return the same thing: a blank screen or a 500 with not one line of explanation. And there is no service status page to tell you whether the problem is theirs or yours¹. So the first job is not to repair anything, it is to work out which of six cases you are in.

There is one distinction that saves time: the portal not working (won’t load, won’t log you in, returns a 500) is one thing. A guest report going out and coming back rejected with a code is another, because there the platform is fine and what fails is the data. The rejection codes, one by one, are in the error-code guide; for the platform in general, the SES.HOSPEDAJES guide.

Is SES.HOSPEDAJES down right now?

The short answer: there is no official way to tell. Spain’s Ministry of the Interior publishes no service status page for SES.HOSPEDAJES, and no account where outages get announced¹. All there is is an email address for technical queries in the Ministry’s own FAQ, [email protected]², and that is for asking questions, not for finding out whether the service is up.

So the check is indirect, and it takes a minute. Open the portal from another network and another device (a phone on mobile data, wifi off, is the fastest test):

• If it loads on the phone but not on your computer, the problem is at your end: network, browser or certificate. Carry on with causes 2 and 3.
• If it loads on neither, it’s down. Nothing on your side to fix.

Before you close the tab, take a screenshot with the time visible: it is your evidence that you tried to file on time.

The 24-hour deadline is not suspended by a portal outage

Don’t sit there refreshing, but don’t treat the deadline as paused either. RD 933/2021 sets the report at 24 hours and provides no exception for the portal being unavailable:

“This communication shall be made immediately and, in any event, within a period of no more than 24 hours, respectively, from the following moments: a) On making the reservation or formalising the contract or, where applicable, its cancellation. b) At the start of the contracted services.”

Neither that paragraph nor the Ministry’s FAQ provides an alternative route while the portal is unavailable. The next paragraph, 6.4, requires communications to be made by telematic procedures and exempts only those hosting on a non-professional basis, who may use non-telematic means “by the procedure to be determined”. If you are a professional, there is no paper channel to fall back on until the platform returns.

What works in your favour is that the outages we see clear in hours rather than days, so retrying later the same day usually keeps you inside the 24 hours. And if an outage eats the whole window, the decree itself separates two breaches that do not cost the same⁴, with the amounts set by Organic Law 4/2015⁵:

• Reporting late is a minor infraction: a fine of 100 to 600 euros.
• Not reporting the guest data at all is a serious infraction: 601 to 30,000 euros.

The whole difference between one bracket and the other is submitting late instead of not submitting. As soon as the service is back, submit, even if you are past the 24 hours.

Guest check-in carries on even when the portal is down

While you are fighting the portal, the guest arrives anyway. If entry is by key box at two in the morning, there is no desk to close and nobody to warn: the stay starts on schedule.

That does not leave you with nothing to do, because the outage hits one of your two duties and not both. Article 5.1 requires you to keep a computerised register with the Annex data, and that is a duty independent of the Article 6 reporting⁶. Collecting the data and holding it does not go through SES.HOSPEDAJES. The only thing waiting on the portal is the filing.

So check-in happens like any other day, and remotely if that is your flow: the Ministry accepts collecting the data by any system that allows its accuracy to be verified, even without physical presence². Link to the guest, the full Annex I fields, a verification (the traveller’s digital certificate, a check against the payment method details, or a code sent to their phone or email), and a signature from everyone over fourteen. When the portal returns, the report only has to go out.

Leaving the collection for when the portal works too is the expensive mistake, and not because of the deadline. If you host professionally, absence of the documentary registers is a serious infraction in its own right, 601 to 30,000 euros, the same classification as not reporting at all⁴. A report filed late costs between 100 and 600 euros; data you never collected because the portal was down that night cannot be fixed the next morning, because the guest has gone. What counts as verification with nobody at the door is in what RD 933/2021 allows without physical presence.

Two-minute checklist when SES.HOSPEDAJES fails

In a hurry? Find what you see on screen in the first column and run the check in the third:

1. The portal is down or under maintenance

What you see: a blank screen, a timeout or a server error, on any device and from any network.

The simplest cause and the first to rule out. The Interior Ministry’s portal has outages and maintenance windows, and it announces them nowhere.

What to do:

1. Open the home page from another device or network, a phone on mobile data for example. If it doesn’t load there either, the problem isn’t on your side.
2. Take a screenshot with the date and time visible.
3. Retry later the same day: a couple of hours of downtime does not put you outside the 24 hours.
4. If the portal is still down when the deadline runs out, submit as soon as it returns and keep the screenshots.

2. The digital certificate fails

What you see: the portal loads, but logging in with your certificate gets you no further than the login screen, or throws a 500 with no explanation.

You log into the portal with the same certificate the establishment was registered with, so any mismatch there locks you out¹. Three mismatches cover almost every case:

• Expired certificate. In our own logins, the portal sometimes answers with a bare 500 without mentioning that the certificate has expired. Check its validity date in the browser.
• Wrong person’s certificate. The registration is tied to a specific holder. If the property belongs to a company and you log in with your personal certificate, it won’t work: you need the company-representative certificate.
• Certificate not installed in this browser. Certificates install per browser, per machine. New computer means reinstalling it.

3. The browser or phone won’t load the portal properly

What you see: the page stays blank, a button does nothing or the signature never completes, and the same portal works fine from another machine.

The Sede Electrónica publishes which browsers it supports, and the list is short: Internet Explorer 9 or later and Edge, Google Chrome, and Mozilla Firefox. Signing a form also requires the Autofirma application installed⁷. Safari and mobile browsers are not on that list.

What to do:

1. Move to a computer with an up-to-date Chrome, Edge or Firefox.
2. Install Autofirma if you are going to sign a registration or an amendment.
3. Clear the site’s cache and cookies.
4. Disable blocking extensions (adblockers, antitracking) for this domain.

4. You are using the wrong set of credentials

What you see: you log into the portal fine but your software returns an authentication failure when submitting, or exactly the other way round.

Registering the establishment hands over two sets of credentials at once, and that is where the confusion starts:

“Once registration is complete, both the credentials for accessing the application and those enabling the communication to be submitted through the automatic procedure via a Web Service are provided.”

They are not interchangeable:

Each set also has its own password, with different procedures for recovering or changing it: the Ministry’s visual guide gives them two separate sections, one for the portal password and one for the web-service password⁸. If your software fails authentication but you can log into the portal fine, or the other way round, you are almost certainly crossing the two sets. How to obtain each one is in the credentials guide.

5. The submission password contains problematic characters

What you see: the software fails authentication again and again with a password you know is the right one, and which works on the portal.

A silent classic. The portal accepts passwords with quotes, accents and other special characters when you create them, but in our own submissions some of those characters break web-service authentication.

What to do:

1. Change the submission password to a long one made only of unaccented letters, numbers and hyphens.
2. Update it in your software at the same moment. A password changed on the portal but not in the tool is the other half of all authentication failures.
3. Check that copying it has not dragged in a space before or after.

6. The report goes through but comes back rejected

What you see: the submission goes out, the platform answers, and the answer is a rejection with a code.

Here the platform works: what fails validation is the data. The reasons repeat, and they come in three kinds: documents that don’t pass validation, dates that don’t line up between reservation and check-in, and empty mandatory fields.

There is a consequence that gets overlooked: a rejected report has not been filed. The 24-hour deadline in Article 6.3 keeps running while you fix the data, so a rejection on the night of the check-in is urgent, not a minor hiccup. Every code has its own specific fix, and they are collected in the SES.HOSPEDAJES error-code guide.

FAQ

Is SES.HOSPEDAJES down today, or won’t it let me log in? Telling a SES.HOSPEDAJES outage apart from a login problem starts with the quickest checks: see whether the portal is down (cause 1) by opening it from another network or device; if it loads but won’t let you log in, it’s usually the digital certificate (cause 2) or the browser (cause 3); and if you can log in but submissions fail, it’s a credentials issue (cause 4).

What if SES.HOSPEDAJES is down and I miss the 24-hour deadline? If SES.HOSPEDAJES is down and you miss the 24-hour deadline, submit as soon as the service returns and keep the screenshots of your attempts with date and time. No rule suspends the deadline because of a portal outage: RD 933/2021 sets the 24 hours with no exception for unavailability. What does change is the severity: reporting late is a minor infraction, 100 to 600 euros, while not reporting at all is a serious one, 601 to 30,000 euros.

Is there an official status page for SES.HOSPEDAJES? No, there is no official status page for SES.HOSPEDAJES. The Ministry publishes no service status page, and the only official address is the technical-query one in its FAQ, which is for asking questions rather than checking the status. The practical check is the one in the first section: try from another network or device and rule out a local problem.

Why can I log into the portal while my software can’t submit reports? You can log into the portal while your software can’t submit reports because web access and telematic submission use different credentials, both handed over when the establishment is registered. Check your software holds the web-service set, with no stray spaces from copying, and that the password hasn’t been changed on the portal.

Submitting to SES.HOSPEDAJES without fighting the portal

Fighting the portal every time a booking lands is optional. With automated submission, guest data is validated before it leaves, so data rejections drop to zero or close to it. And every submission is logged with the Ministry’s response: exactly the paper trail you want on the day the portal goes down. That is what RegistroViajero does. Digital check-in, validation of the RD 933/2021 fields, and submission to SES.HOSPEDAJES without the portal costing you sleep.

Want to see it? See how RegistroViajero works.

Exact menu names on the SES.HOSPEDAJES portal may vary between Ministry updates. This guide reflects general behaviour at the date of publication.