Correct URL for Diagrams from diagrams.net
Hi Community,
im confused with embeding Diagrams from diagrams.net. In the documentation https://www.jetbrains.com/help/youtrack/server/2024.3/embedding-content.html#-wdgh58_202 it says:
- Copy the URL of your diagram from diagrams.net from the browser tab.
- Create an IFrame view of the diagram. On the page of the diagram, click File > Embed > IFrame. Configure the options and click the Create button. From the generated HTML code, copy the diagram URL.
But both url do not work for me. However, i click Datei(file)→Veröffentlichen(publish)→Verknünpfung(link), this url works for me. Just wonder why…Any ideas? Thx in advance!!
Please sign in to leave a comment.
Hi, thanks for spotting that! I've shared this with our documentation team to improve these instructions. The File > Publish > Link path seems to be the correct way to obtain that URL now. File > Embed > IFrame will also work, provided that you copy just the URL (from
src="url-goes-here") .Hi Stanislav Dubin,
Thank you for your response. I have an additional question. We definitely want to use diagrams.net but are not comfortable with saving our diagrams in the cloud. Since we are using the server version of YouTrack, is there a solution to integrate diagrams.net into our own server environment?
Best
Mickeychen4728 there is now a third-party solution for diagrams available in the YouTrack app marketplace: Diagramm Editor. It can be downloaded and used locally with YouTrack Server. Feel free to give it a try!
Hi Stanislav Dubin,
thx for the info!!! Still have some question:
1. is this plg-in for free?
2. im trying to install it in our staging enviroment, but it has hard time opening this in the browser.
But its really quick to be opened in our production
But to test the installation is essential for us. Do you know any potential reasons why its not loading in our staging enviroment?
Thx in advance!
Mickeychen4728 the app is currently free, although it will be up to the vendor to decide on the possible monetization moving forward. Regarding the problem you mentioned, perhaps the browser console can shed some light on why this happens (you might see some errors there). In any case, I would rather suggest reaching out to the plugin vendor—you can do it on the Marketplace page > Report Issue. They've also mentioned this on the Marketplace page, which may be relevant: