"Network Error" when accessing a base

saschavalentin · December 20, 2021, 7:40am

I know there was another post (Network error.. Developer edition on own VP server behind a web server) like the one I´m gonna write now and there is also one part in the official manual dealing with this issue (Developer Edition - SeaTable Admin Manual), but none of them helped me yet.

I just installed seatable-ee via docker on a vserver on Contabo. Everything worked fine and I can access it…

Even creating a new base works…

But as soon as I want to open this base a “Network Error” appears…

Running the developer tools the debugger shows these two errors:

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://5.189.147.230/dtable-server/dtables/6d8e0c57-5843-4441-b6ff-9f5b5029e022?lang=de. (Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt). Statuscode: 200.

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://5.189.147.230/dtable-server/dtables/6d8e0c57-5843-4441-b6ff-9f5b5029e022?lang=de. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

I´m a bit despaired because nothing I did helped me get rid of this error. So I hope someone can help me with this. Any ideas what to do?

Karlheinz · December 20, 2021, 8:15am

Welcome to the SeaTable forum.

The interface you see is on the so-called dtable-web server and the bases are stored on dtable-server. So when you can see the interface and can create a new base, it means the dtable-web is running OK. However, in your case, the access to dtable-server is blocked due to CORS problems. The cause could be, that you use a custom domain but didn’t specify the dtable-server address separately.

I see you are using a custom domain:
Did you specify the dtable-server domain in the dtable_web_settings.py?

You should change this line:

DTABLE_SERVER_URL = 'http://5.189.147.230/dtable-server/'

dtable_web_settings.py - SeaTable Admin Manual

saschavalentin · December 20, 2021, 8:57am

Hello Karlheinz (a bit strange to talk English to someone obviously being german ),

thanks for you fast reply.

Yes, the concerned lines are specified in the dtable_web_settings.py. But as I´m no versed master of network issues there would be one question: Does it make a difference if the DTABLE_SERVER_URL points to an IP address or a real URL. Concrete: In the docker-compose file I put the IP address as the host name and therefore all teh URLs in dtable_web_settings.py are pointing to that direction. In case of the dtable-web this seems to work. And because of DTABLE_SERVER_URL is the same as DTABLE_WEB_SERVICE_URL except adding /dtable-server/ as folder this should work too??

rdb · December 20, 2021, 8:11pm

What matters are the parameters in the configuration files. The parameters for Let’s Encrypt and host address in the Compose file aren’t relevant anymore after the initialization.

Why don’t you post your configuration here? For an experience admin, a configuratin file is a lot simpler to read than plain prose.

I guess the general problem is that you access dtable-web with https and you try to access dtable-server with http. Possible?

“Little princess” is not necessarily a cute little girl.

saschavalentin · December 21, 2021, 6:13am

Hello Ralf,

as far as I can see all routes are set to http. Here is the dtable_web_settings.py:

# for dtable-server
DTABLE_SERVER_URL = 'http://5.189.147.230/dtable-server/'
DTABLE_SOCKET_URL = 'http://5.189.147.230/'

# for dtable-web
DTABLE_WEB_SERVICE_URL = 'http://5.189.147.230/'

# for dtable-db
DTABLE_DB_URL = 'http://5.189.147.230/dtable-db/'

# for seaf-server
FILE_SERVER_ROOT = 'http://5.189.147.230/seafhttp/'

And the dtable_db.conf:

[general]
host = 127.0.0.1
port = 7777
log_dir = /opt/seatable/logs

[storage]
data_dir = /opt/seatable/db-data

[dtable cache]
dtable_server_url = "http://127.0.0.1:5000"
total_cache_size = 100

Do you need another one? Maybe the error from the debugger is helpful?

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://5.189.147.230/dtable-server/dtables/6d8e0c57-5843-4441-b6ff-9f5b5029e022?lang=de. (Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt). Statuscode: 200.

Thanks for your help!

rdb · December 21, 2021, 12:48pm

This is what I see when accessing the IP address:

Why is there an Apache answering?
How’s the Apache configured?
How’s the Nginx configured - the one started by the Compose file?

saschavalentin · December 21, 2021, 2:33pm

Oh, sorry, I should have mentioned that the seatable docker listens on port 9020.

The Apache is running because Contabo offered an Ubuntu system with or without LAMP. If this is a problem, I could reinstall without the LAMP. That is no need for me.

Here´s a link to the nginx.conf: Untitled - Pastebin.com

speicherbox · December 22, 2021, 10:33am

In this case, you should have to add the Port to the configuration like this as your SeaTable installation does not listen on Port 80 (default http).

# for dtable-server
DTABLE_SERVER_URL = 'http://5.189.147.230:9020/dtable-server/'
DTABLE_SOCKET_URL = 'http://5.189.147.230:9020/'

# for dtable-web
DTABLE_WEB_SERVICE_URL = 'http://5.189.147.230:9020/'

# for dtable-db
DTABLE_DB_URL = 'http://5.189.147.230:9020/dtable-db/'

# for seaf-server
FILE_SERVER_ROOT = 'http://5.189.147.230:9020/seafhttp/'

saschavalentin · December 23, 2021, 10:47am

@speicherbox : You are my greates christmas present this year So many thanks for this solution. Adn in the end so easy to solve. Thanks again and all the best wishes for your christmas and a happy, healthy new year.

system · December 25, 2021, 10:48am

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.