-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tectonic throws DNS error when trying to fetch web-bundle #949
Comments
I found a workaround by specifying an alternative web-bundle URL like: $ pandoc --pdf-engine tectonic --pdf-engine-opt='-w https://archive.org/services/purl/net/pkgwpub/tectonic-default' README.md -o README.pdf The URL was copied from this thread: #685 (comment) |
See #951 . The domain was expired for about 2 hours. It should be fixed now, maybe taking a few hours for DNS to propagate through the system. |
Can confirm that it works again and thanks for the quick reply! |
I am currently facing the same error. Is this a temporary issue? |
@heyarne Generally, if you are experiencing a network-related issue like this, it is much more likely that it is on your side than the Tectonic side. At the moment everything in the Tectonic web services appears to be stable and running normally. |
Can confirm that it works now. Sorry for the noise! |
Tectonic throws a DNS error when trying to compile a document because it cannot resolve
relay.fullyjustified.net
.I'm a bit surprised thattectonic
requires some external service to be online.Anways, you can find a minimal example to reproduce the problem below:
I was able to reproduce the problem locally as well as in Docker. My
Dockerfile
looks like this:The text was updated successfully, but these errors were encountered: