In MiKTeX 2.9 Package manager, when I'm trying to synchronize it writes me a message: "The remote package repository is not online...", but I'know server is online (I can use FTP to download packages manualy). When I'm trying to change repository it shows me empty list. Like that: Empy list

What can I do to fix this without manual downloading packages from repo?

  • 2
    Wait. Imho the main server with the list of repositories is down, and normally there is a reason when Christian disables it. If you badly need a package you can download it from CTAN (along with miktex-zz-XXX-files which contains the database info) and use a local repository. Commented Jun 20, 2015 at 12:18
  • 1
    Christian wrote in the miktex mailing list " The server (repositories) is (are) currently unstable because some maintenance needs to be done. Everything should be in its right place next week. Enjoy the weekend..." Commented Jun 20, 2015 at 21:38
  • @UlrikeFischer It seems that the problem still persists Commented Jul 8, 2015 at 15:45
  • @Anoldmaninthesea. : No it was fine the last two weeks. But it seems down now. Commented Jul 8, 2015 at 15:48
  • @Anoldmaninthesea.: There is a message on the website that there is a problem: miktex.org. Commented Jul 8, 2015 at 16:09

2 Answers 2


Sometimes the miktex maintainer disables the main server with the list of repositories e.g. when a serious bug has appeared to avoid that people download a broken package. Sometimes the main server is simply down.

In both cases the best is to wait and to check if there are messages on the miktex website or the miktex mailing list.

If you badly need a package you can download it from CTAN from the miktex package folder (http://mirrors.ctan.org/systems/win32/miktex/tm/packages/) along with the "package databases" (two miktex-zz-XXX-files). Put everything in some empty folder and use it as local repository.


If the miktex api is actually online and displaying valid mirrors, the api might just be bugged. At the time of writing both the GetRepository4 and the VerifyRepository2 action in the api seem to be broken. However, the PickRepository4 action works fine, and since the api returns it, the application assumes it is a valid repository. You can verify if that is the case for you by opening a command console and running mpm --pick-repository-url in the appropriate directory. If it displays an url instead of an error this solution should work for you.

Instead of doing the following steps, you can simply uninstall miktex, and check the option that it should clean up after itself. It will delete all temporary files, and the register keys it uses. The downside is that after re-installing miktex, you'll need to install all packages again. Yaaaaaay... :(

Editing the register might cause all kinds of problems, including all kinds of things crashing. Always make a backup before editing the register. If in doubt, go for the safe route and read the previous paragraph.

To get your installation working again, open regedit.exe (e.g. via Windows + R).

Navigate to Computer\HKEY_CURRENT_USER\SOFTWARE\MiKTeX.org\MiKTeX\2.9\MPM\. It should contain three keys, namely RemoteRepository, RepositoryReleaseState and RepositoryType. Delete these keys.

MiKTeX package manager (MPM) will now default to asking the api for the closest repository instead of using the one you previously defined, which will work in most cases.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .