# Cport issue on large protein
**URL:** https://ask.bioexcel.eu/t/cport-issue-on-large-protein/4297
**Category:** HADDOCK
**Created:** [May 3, 2023, 1:42pm UTC](https://ask.bioexcel.eu/t/cport-issue-on-large-protein/4297 "2023-05-03T13:42:34Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Andrea\_Spitaleri](https://ask.bioexcel.eu/u/Andrea_Spitaleri)
#### Post date: [May 3, 2023, 1:42pm UTC](https://ask.bioexcel.eu/t/cport-issue-on-large-protein/4297/1 "2023-05-03T13:42:34Z")
Hi
I am trying to use cport for this 8eeb protein using either the PDB import or the pdb fixed by CHARMM-GUI server (some residues are missing).
I am getting this error for job 19729511 using PBD import (8eeb):
**Failed predictors**
ProMate, PIER, SPPIDER, PINUP
PINUP has got seg fault so the problem is the size I guess. The other servers no idea:
```auto
**ProMate**
Exception in thread ProMatePredictionInput=>InterfacePredictionResult:
'NoneType' object has no attribute 'rfind'
**PIER**
Exception in thread PIERPredictionInput=>InterfacePredictionResult:
**SPPIDER**
Exception in thread SPPIDERPredictionInput=>InterfacePredictionResult:
```
Any suggestion? Since the protein is large but it is a transmembrane protein, I could in principle restrict the analysis on a small region of if, i.e. the extracellular one. Is it possible?
---
### Author:  [@amjjbonvin](https://ask.bioexcel.eu/u/amjjbonvin)
#### Post date: [May 3, 2023, 1:58pm UTC](https://ask.bioexcel.eu/t/cport-issue-on-large-protein/4297/2 "2023-05-03T13:58:15Z")
> Any suggestion? Since the protein is large but it is a transmembrane protein, I could in principle restrict the analysis on a small region of if, i.e. the extracellular one. Is it possible?
Possibly. But there are currently issues with CPORT, both security ones and also several of the servers it is accessing are no longer working.Because of that we have discontinued the current server.
We are currently working on an updated version querying modern servers. But it will take some time before that one is ready for use in server form.
The code is however available on GitHub already: [https://github.com/haddocking/cport](https://github.com/haddocking/cport)
---
### Author:  [@Andrea\_Spitaleri](https://ask.bioexcel.eu/u/Andrea_Spitaleri)
#### Post date: [May 3, 2023, 2:32pm UTC](https://ask.bioexcel.eu/t/cport-issue-on-large-protein/4297/3 "2023-05-03T14:32:09Z")
Thanks Alexandre. I will have look to the github. The modern servers you are referring to are thone reported in the cport github?
---
### Author:  [@Andrea\_Spitaleri](https://ask.bioexcel.eu/u/Andrea_Spitaleri)
#### Post date: [May 3, 2023, 4:36pm UTC](https://ask.bioexcel.eu/t/cport-issue-on-large-protein/4297/4 "2023-05-03T16:36:08Z")
Actually using the pdb from CHARMM-GUI worked (almost):
```auto
the following predictors finished successfully
cons-PPISP (Chen and Zhou, 2005)
PINUP (Liang et al., 2006)
**Failed predictors**
ProMate, PIER, SPPIDER
```
Fair enough.
One more question on WHISCY. I have run blastp to get a set of hits and then aligned them using either MUSCLE or MAFFT. The aligned fasta to WHISCY give the following error:
```auto
whiscy_setup [ERROR] HSSP file could not be generated
ERROR: Setup has failed
```
Example attached.
[clustalo-R20230503-171249-0115-13653860-p2m.fasta.txt](https://ask.bioexcel.eu/uploads/short-url/d9RKaKJiQn9bpD1vix8i9YNuavT.txt) (6.5 KB)
---
### Author:  [@amjjbonvin](https://ask.bioexcel.eu/u/amjjbonvin)
#### Post date: [May 4, 2023, 7:00am UTC](https://ask.bioexcel.eu/t/cport-issue-on-large-protein/4297/5 "2023-05-04T07:00:38Z")
> Thanks Alexandre. I will have look to the github. The modern servers you are referring to are thone reported in the cport github?
Yes