Error starting nitrogen project: Bad value on output port 'tcp_inet'

Erlang Platform & Framework Forums Nitrogen Forum
, , , ,
1

When typing ‘bin/nitrogen console’ into my terminal the normal text scrolls then when i try accessing the root page i get:

 =PROGRESS REPORT==== 12-Dec-2022::17:02:41.303590 ===
     application: nitrogen
     started_at: 'ookma-kyi-core@127.0.0.1'
 
 =INFO REPORT==== 12-Dec-2022::17:03:27.980212 ===
 Body: []
 Query: []
 =INFO REPORT==== 12-Dec-2022::17:03:28.028507 ===
 Recaching Template: ./site/templates/bare.html
 
 =ERROR REPORT==== 12-Dec-2022::17:03:28.080745 ===
 Bad value on output port 'tcp_inet'
 
 
 =INFO REPORT==== 12-Dec-2022::17:03:28.084095 ===
 Body: []
 Query: []
 =ERROR REPORT==== 12-Dec-2022::17:03:28.084728 ===
 Bad value on output port 'tcp_inet'
 
 
 =INFO REPORT==== 12-Dec-2022::17:03:28.088548 ===
 Body: []
 Query: []
 =ERROR REPORT==== 12-Dec-2022::17:03:28.089187 ===
 Bad value on output port 'tcp_inet'
 
 
 =INFO REPORT==== 12-Dec-2022::17:03:28.092824 ===
 Body: []
 Query: []
 =ERROR REPORT==== 12-Dec-2022::17:03:28.093751 ===
 Bad value on output port 'tcp_inet'
 
 
 =INFO REPORT==== 12-Dec-2022::17:03:28.097430 ===
 Body: []
 Query: []
 =ERROR REPORT==== 12-Dec-2022::17:03:28.098055 ===
 Bad value on output port 'tcp_inet'
 
 
 =INFO REPORT==== 12-Dec-2022::17:03:28.101345 ===
 Body: []
 Query: []
 =ERROR REPORT==== 12-Dec-2022::17:03:28.102214 ===
 Bad value on output port 'tcp_inet'
 
 
 =INFO REPORT==== 12-Dec-2022::17:03:28.105805 ===
 Body: []
 Query: []
 =ERROR REPORT==== 12-Dec-2022::17:03:28.106822 ===
 Bad value on output port 'tcp_inet'
 
 
 =INFO REPORT==== 12-Dec-2022::17:03:28.111530 ===
 Body: []
 Query: []
 =ERROR REPORT==== 12-Dec-2022::17:03:28.112100 ===
 Bad value on output port 'tcp_inet'
 

 =INFO REPORT==== 12-Dec-2022::17:03:28.115242 ===
 Body: []
 Query: []
 =ERROR REPORT==== 12-Dec-2022::17:03:28.115843 ===
 Bad value on output port 'tcp_inet'
 
 
 =INFO REPORT==== 12-Dec-2022::17:03:28.119530 ===
 Body: []
 Query: []
 =ERROR REPORT==== 12-Dec-2022::17:03:28.120106 ===
 Bad value on output port 'tcp_inet'

image
image1920×1030 32.6 KB

I am on WSL2 and already tried a full reinstall to no success. I am running the inets server if that helps.

2 Likes
2

If you have solved this I would love to know what you did. I have the same issue like you. On a fresh Fedora install.

2 Likes
3

no solution, but using cowboy instead of inets works for me. (I get the same error using inets, Erlang 25.0 on macOS).

If you follow Nitrogen - Documentation just use make rel_cowboy instead of make rel_inets. The rest stays the same.

3 Likes
4

Interesting both of you.

The Body and Query messages are troubleshooting lines in Simple Bridge - I should get them removed today.

But the fact that so many are running into issues with different platforms is a little concerning. I’d been chatting with the OP in slack, so I thought it was just a WSL problem (I’m struggling to get WSL working in a VM running in Linux, so there’s that).

I may fire up a fedora VM and see if I can replicate the crash, though. That shouldn’t be the case.

Thanks for the reports!

3 Likes
5

Yes, cowboy did work. Thank you for the workaround solution. :slight_smile:

2 Likes
6

IDK if it helps but I have also tried it in a Ubuntu VM and had the same issue there with the inets webserver.
Thank you for looking into that.

1 Like
7

@fizfaz Thanks for the workaround.

@gumm What are the differences between inets and cowboy?

1 Like
8

Hey Folks, just following up. The inets crash has been fixed in mainline simple_bridge - sorry for that - that’s 100% on me.

@Ookma-Kyi as for the differences between the webservers, I briefly cover that on Nitrogen - Downloads if you click the little link that says “Not sure which webserver to use?” While I make the effort to keep Nitrogen webserver agnostic, practically, most projects seem to either use Cowboy or Yaws in production.

3 Likes
9

Silly question, but is the fix with nitrogen or inets? I checked the nitrogen repo and did not see an update.

1 Like
10

Actually never mind. You did your magic on your end lol.
Just tried it with inets and it works now.
Thank you! :slight_smile:

2 Likes
11

Yeah, the bugfix was in simple_bridge, that’s why you’re not seeing the commit in nitrogen or nitrogen_core.

2 Likes