-
Notifications
You must be signed in to change notification settings - Fork 23
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
Plugins in local instance #1549
Comments
I don't know if the problem is specifically with Seqviz. Here is a screenshot of my admin page setup: This gives me the following on the console (when refreshing the component page):
To me it seems like I'm not able to point to things correctly when using port numbers (as in trying to connect to :8085 and :8081), since when using the plugin name it kind of works. I still get the error on Seqviz though, which I imagine happens because of trying to connect to localhost:7777 on the way back and not managing to. I think it might be related to Common Problem 2 on the wiki:
but it's a bit hard for me to translate the solution to synbiohub from stack overflow and docker, because I lack the experience in docker/docker-compose. I understand I need to try "host network mode" on containers, but where specifically do I do this? Stack overflow says:
Should I change something on the docker-compose .yml files? Or do something as a command when I boot synbiohub? Also, I'm not sure why the online plugins didn't work. SynBioHub was up and should be working. Thanks for the help! |
I got a bit more insight into what's happening. With the name assignment on the admin page (or using the "host.docker.internal:host-gateway" extra host on the synbiohub docker yml) I can successfully request the plugins. The problem now is that they're still trying to reach information from an SBOL component which has a URL starting in "http://localhost", so I still get a connection error there. I tried declaring the extra host on the plugin container yml, but didn't manage to make it work. I'm not sure if that would work anyway because even if the plugin can access the alternative host, it's going to look for localhost:7777 because that's what is in the SBOL url. I managed to reach the online plugins too. I was just using "http" instead of "https" on the Accurat one and the SBHub Seqviz was just non-responsive (in the main SynBioHub too). |
SeqViz recently stopped working for us. I'm not sure why, and I've not had time to fully debug it (bit swamped on a few others things right now). Right now, we have taken it down, since its failing was causing problems to SBH. It is probably best to avoid using this one until we can figure out why it suddenly stopped working for us. |
I believe my problem is a bit more general than just Seqviz not working. I'm getting an error from a plugin trying to get SBOL object data from localhost:7777 because that's what is in the SBOL URL. I know this is exclusive to local instances, but would be nice if it could be solved. |
We recently got SeqViz up and running again. However, I think you are right that you will likely continue to have issues due to the fact that plugins are trying to communicate with localhost. I'm actually not very sure how to access external plugins from a local instance. I've never done this myself, and it is also outside my expertise. I think we usually test plugins by running them locally. I'm going to connect you to @JMante1 and @zane-perry by email to see if they can help. |
Hi all,
I'm trying to play around with a local instance of synbiohub and am having some problems getting plugins to work.
I'm trying to get the seqviz plugin to work, and I'm getting a connection error:
error: connect ECONNREFUSED 127.0.0.1:8085 {"errno":"ECONNREFUSED","code":"ECONNREFUSED", "syscall":"connect","address":"127.0.0.1","port":8085}
I also had a more general question about plugins: Where are all plugins actually located? I'm specifically looking for the Accurat plugins to test on this local instance, but I wouldn't know how to call and pull them.
The text was updated successfully, but these errors were encountered: